Changes for page 271 - Secure Ship
Last modified by Erik Bakker on 2026/06/29 09:20
From version 33.1
edited by Erik Bakker
on 2022/12/06 16:03
on 2022/12/06 16:03
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 (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 89-PrivateEye1 +271 - Secure Ship - Content
-
... ... @@ -1,24 +1,22 @@ 1 -Th ereleasebringsaprivatestore to our communityandmakes the latestruntime image availablefor ourcustomersrunning on the3rdgeneration architecture. Furthermore,we introduceseveral improvementstoour3rd generationruntimeanditsinteractionwith theportal.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.189 - Private Eye.WebHome||target="blank"]]. 4 -=====New features===== 5 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Release blog>>Main.Release Information.Runtime Images.V1~.~1~.~0.WebHome||target="blank"]]. 3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.271 - Secure Ship.WebHome||target="blank"]]. 6 6 7 -=====Minor changes===== 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) 8 8 9 -* General: Code mapping is now available for models migrating to the 3rd generation runtime. 10 -* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform. (#785) 11 -* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you. 12 -* Deploy - Deployment plan: For 3rd generation runtimes we have changed the restart behavior in case of startup problems. This means that when a runtime is being deployed, which is constantly crashing and thereby causing problems, the restart of the runtime is limited to just five times. (#720) 13 -** After five times, the runtime will remain in the stopped state. 8 +==== Minor Changes ==== 14 14 15 -====Bug fixes==== 16 -* Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717) 17 -* Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718) 18 -* Deploy - Deployment plan: Before when you tried to deploy a Release via the Deploy functionality the widget could crash randomly. With this fix we ensured the widget will always load correctly. (#362) 19 -* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703) 20 -* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore. 21 -* Manage - Error Dashboard: Solved a problem that caused a user to see a general error when opening the Manage Dashboard while running a 3rd generation runtime architecture. 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) 22 22 23 -====Remarks==== 24 -* Mendix Runtime has been upgraded to Mendix 9.19.0. 14 + 15 +==== Bug fixes ==== 16 + 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)