Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55

From version 164.1
edited by Carlijn Kokkeler
on 2023/11/23 08:56
Change comment: There is no comment for this version
To version 273.1
edited by Carlijn Kokkeler
on 2024/07/16 15:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +225 - Pop-up Party
Content
... ... @@ -1,28 +1,26 @@
1 -In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
1 +During our recent sprint cycle
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.225 - Pop-up Party||target="blank"]].
4 4  
5 -=====New features=====
5 +====New features====
6 6  
7 -* Deploy - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties.
8 -* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 -* All - The next generation architecture is the default now. New models will use this generation as default.
10 10  
11 -=====Minor changes=====
8 +====Minor changes====
9 +* Design - Architecture: If a model does not have a license for a pattern, the model contact now has the option to delete the process container of that given pattern. (#1297)
10 +* Design - Settings: When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment. (#787)
11 +* Deploy - Releases: A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before.
12 +* Create - Flow Designer: Added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
13 +* Create - Flow Designer: Improved the error message when configuring an Infinispan Cache Manager with 'TCP-ping' transport type, when the list of peer hosts are passed in invalid format. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
14 +* Create - Resources: When bumping a new version of flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description. (#1326)
15 +* Create - Flow Designer: Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'. (#795)
16 +* Deploy - Architecture: For clarity purposes, a confirmation pop-up will be shown when deleting routes.
17 +* Manage - Explore: The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it.
12 12  
13 -* Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
14 -* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
15 -* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
16 16  
17 17  ====Bug fixes====
18 -
19 -* Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
20 -* Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped.
21 -* Manage - Monitoring - We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
22 -
23 -
24 -
25 -
26 -
27 -
28 -
21 +* Design - Message mapping: We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows. (#1357)
22 +* Create: The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it. (#1159)
23 +* Create - Flow Designer: Editing a namespace used in a message definition automatically updates the message definition & transformations.
24 +* Create - Flow Designer: The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with \ instead of /. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain / again. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
25 +* Manage - Monitoring: The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
26 +* All - Updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.