Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 46.1
edited by Erik Bakker
on 2023/01/31 14:51
Change comment: There is no comment for this version
To version 116.1
edited by Carlijn Kokkeler
on 2023/10/11 15:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +206 - Situational Deployment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,53 +1,44 @@
1 -The release introduces a lot of small fixes as a result of our "hackathon" efforts. Subsequently we will release several 3rd generation runtime offerings.
1 +In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.191 - Fifty Fifty.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Situational Deployment.WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 -* Deploy - Architecture: We added the possibility to register network shares in your container volume settings. This enables the use of network shares without having to mount them manually on the host machine and then again on container level. This option is only available for 3rd generation runtimes that run on-premises.
7 -* Deploy - Containers: In Deploy containers a ‘Debug’ option is added for flows on the 3rd generation eMagiz runtime.
8 -** This option will temporarily be available for users on the next generation runtime. It allows to easily wiretap messages from channels in a flow to a queue, which can the be browsed using the queue browser. One flow can be wiretapped at the time, per container.
9 -** To use this option, the model must be fully migrated to Gen3, including the JMS which also needs to be reset. Additionally only flows in a container that has the Gen3 Debugging components inside of the associated container infra flow can be debugged. For more information on how to setup debugging on Gen3, please consult the documentation.
10 -* Manage - Alerting: There are 4 new types of triggers available for Model in G3.
11 -** Error Message is to evaluate the headers of the original message which resulted in an error.
12 -** Log Keyword is to evaluate logging messages. You can provide a one or several words which you expect in your logging events.
13 -** Queue Consumers is to configure for queues where more than 1 consumer is expected.
14 -** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
15 -** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages that are expected to pass through the flow.
16 16  
17 17  =====Minor changes=====
18 18  
19 -* Data-Limit: Set data limit per environment.
20 -* Login page: Login page /login.html now redirects to the real login page /p/login. (#671)
21 -* Create - Flow designer: Removed the unnecessary refresh button from the component creation pop-ups. (#858)
22 -* Create - Flow designer: Properties in the property overview pages are sorted as Test/Acceptance/Production. (#804)
23 -* Create - Flow designer: We improved validation and help text on Wss4J interceptors components. (#733)
24 -* Create-Flow testing: Improved the help text when adding a header type for a test message. It now clearly states which types of Java classes can be used along with some examples. (#742)
25 -* Deploy - Releases: Setting a release as active by pressing the deploy button creates an entry in the deploy history. (#823)
26 -* Deploy - Releases: We improved the notification popups of failed machine deployments.
27 -* Deploy - Releases: We added column sorting to the popup showing the missing properties. (#860)
28 -* Deploy - Architecture: New cloud slots have their auto-upgrade value set to true by default. (#841)
29 -* Deploy - Architecture: A docker container's status is more visible when you open detail page of the docker container.
30 -* Deploy - Architecture: On the detail page about an instance, the state of the instance is now visible. (#699)
31 -* Deploy - Architecture: We changed the wake-up time of cloud slots on Fridays to 6:00 UTC, so that they no longer fall within our regular deployment windows. (#559)
32 -* Deploy - Architecture: We added runtime memory checks to ‘Apply to environment’, to prevent invalid deployments. (#719)
33 -* Deploy - Properties: We improved runtime selection when copying properties. (#796)
34 -* Manage - Explore: Improved the displayed error message when a message could not be loaded in the message redelivery screen. (#696)
35 -* Manage - Explore: “Save as test message” button opens a pop-up that allows you to edit your test message’s name, description, content and headers before saving it.
36 -* Manage - HTTP statistics: Fixed a typo in HTTP statistics dashboard. (#856)
37 -* Manage - Alerting: By default, no filter is applied to Status when navigating to Notifications, or resetting the filters on Notifications. (#486)
8 +* Design - Framework: The framework used in the flow designer has been updated to the latest version.
9 +* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier.
10 +* Create - SSL: Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
11 +* Deploy - Architecture: The title of the 'apply to environment' action for changing topic retention size has been changed to be less confusing.
12 +* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum.
13 +* Deploy - Deployment plan: A change in the memory settings of the JMS triggers a redeployment of the container.
14 +* Deploy - Logging: New logging feature enabling us to make better choices in deprecating old encryption standards.
15 +* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
16 +* Deploy - Release properties: The description of a property can be changed by editing the property.
17 +* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
18 +* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
19 +* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
20 +* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment.
21 +* Manage - Alerting: Inactivated users should be removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
22 +* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes.
23 +* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default.
24 +* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
25 +* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action.
26 +* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.
38 38  
39 39  
40 40  ====Bug fixes====
41 41  
42 -* Design - Solution design: We hide systems without functional integration now. (#714)
43 -* Create - API Gateway: Security header case insensitive
44 -* Create - Flow designer: Enabling redelivery for you integration is applied after resetting your offramp and exit flow. Before this change, you needed to remove and add the integration to Create phase to apply this setting.
45 -* Deploy - Containers: Applied styling to the error pop-up with the list of reasons why a runtime can’t be deleted to make it easier to read. (#546)
46 -* Deploy - Architecture: Deploying your model to the cloud for the first time, required you to press ‘Apply to Environment’ twice. This is no longer the case. (#508)
47 -* Deploy-Volumes: Network volumes visible when container not deployed.
48 -* Manage - Monitoring: Fix typo in Event Proccessors Metrics. (#835)
31 +* Design - Store: We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
32 +* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
33 +* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
34 +* Design - Store: We fixed an issue that static copies were missing when importing store items.
35 +* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.
36 +* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
37 +* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release.
38 +* Manage - Monitoring: It is now possible to search on messages using partial search words in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
49 49  
50 -====Remarks====
51 51  
52 -* Mendix Runtime has been upgraded to Mendix 9.21.0.
53 53  
42 +=====Infra and image changes=====
43 +
44 +* No infra and/or image changes is this release.