Changes for page 271 - Secure Ship
Last modified by Erik Bakker on 2026/06/29 09:20
From version 165.1
edited by CarlijnKokkeler
on 2023/12/04 15:30
on 2023/12/04 15:30
Change comment:
There is no comment for this version
To version 342.1
edited by Erik Bakker
on 2026/06/29 09:03
on 2026/06/29 09:03
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -21 0-DeploymentDelights1 +271 - Secure Ship - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,28 +1,22 @@ 1 - In thelastsprintcycle, we focusedonimprovingthespeedofthedeploymentplanandmakingthe nextgenerationarchitecture thedefault. On top of that,wehaveworkedtorelease new cloudtemplatesfor DockerSingleLaneand DockerDoubleLane,to introduce fastermachineboot up and improved auto-healing.Moreover,weprocessedseveralfeedback itemsanddid somebug fixes.1 +This release includes improvements to our certificate rotation mechanism that affect all customers using our event streaming offering. On top of that, new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** are released. Furthermore, additional accelerants for all integration developers are here. This includes improvements in how we assist users in Design, Create, and Deploy. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.21 0-Deployment Delights||target="blank"]].3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.271 - Secure Ship.WebHome||target="blank"]]. 4 4 5 -=====New features===== 5 +==== New Features ==== 6 +* Create - Flow Designer: When copy-pasting flow components with support objects, if a similar support object exists in the target flow, you can choose whether to copy the support object or re-use the existing one. (#978) 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. 8 +==== Minor Changes ==== 10 10 11 -=====Minor changes===== 10 +* Design - API Catalog: Removed the “Server” button from this overview, along with all unique configuration related to it, as the button no longer served a function. (#) 11 +* Create - Flow Designer: Selecting a parameter when configuring the XSLT parameters of the XSLT transformer can be done with a dropdown. (#1026) 12 +* Deploy - Containers: The “flows that should run on” overview has been restructured to display the main information by default, with an option to show additional information if needed. Furthermore, updated the styling according to our best practices. (#1768) 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 -====Bug fixes==== 15 +==== Bug fixes ==== 18 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 - 17 +* Create - Add Integrations: A more informative message is shown to the user if and when an automated flow configuration has failed. Additionally, the SOAP integrations can be recreated and edited. (#1377) 18 +* Create - Add Integrations: Fixed a specific case where changing a system to be a Mendix connector in the design phase did not correctly influence the deploy phase. 19 +* Create - Overview: We allow users to open (and reset) connector infra flows for on-premises API systems via the context menu. This makes the navigation to these connector infra flows consistent across patterns. (#1297) 20 +* Create - Flow Designer: A JMS outbound channel adapter can be saved without getting an alert when using a destination expression. 21 +* Create - Flow testing: XML test messages created based on a message definition will now contain randomized data. 22 +* Deploy - Releases (Swagger UI): Ensure that when you click the “Swagger UI” button in Deploy Releases, you are always redirected to the corresponding Swagger UI page, not the home page of our platform. (#1797)