Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 183.1
edited by Carlijn Kokkeler
on 2024/01/03 10:04
on 2024/01/03 10:04
Change comment:
There is no comment for this version
To version 247.1
edited by Carlijn Kokkeler
on 2024/05/21 12:11
on 2024/05/21 12:11
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -21 1-LogLuminary1 +221 - Swift Shift - Content
-
... ... @@ -1,27 +1,18 @@ 1 -In the last sprint cycle, we focused on improving several aspects related to overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimesand flowversionsin the missing properties overview, and see which runtimes will be restartedorredeployedin a pop-up displayed whenstarting the deployment plan.Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase.1 +In the last sprint cycle, we have worked on . 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.21 1-LogLuminary||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.221 - Swift Shift||target="blank"]]. 4 4 5 -=====New features===== 5 +===== New features ===== 6 6 7 -* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines. 8 -* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 7 +* Q & A: Search results are now persisted when pressing the back button after opening a question in the community Q & A. (#1324) 8 +* Catalog: We have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation. 9 +* Design - CDM/System message: A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute. (#151) 10 +* Design - System message: Moving an attribute in the datamodel is now directly shown in the tree structure as well. (#151) 11 +* Design - CDM/API Data model/ES data model and system message: The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype. (#151) 12 +* Deploy - Deploy release: When executing a start/stop action on a group, the description of the step now contains the name of the group. 13 +* Deploy - Architecture: When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group". 9 9 10 -=====Minor changes===== 11 - 12 -* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 13 -* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment. 14 -* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high. 15 -* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917) 16 -* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards. 17 -* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start. 18 - 19 -====Bug fixes==== 20 - 21 -* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. 22 -* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks. 23 -* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 24 -* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container. 25 -* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108) 26 - 27 - 15 +===== Bug fixes ===== 16 +* Design - System messages: When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. (#140) 17 +* Deploy - Containers: The delete behaviour of containers in the container overview has been improved. (#1053) 18 +* Deploy - API Gateway: We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme.