Changes for page 271 - Secure Ship
Last modified by Erik Bakker on 2026/06/29 09:20
From 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
To version 85.1
edited by Erik Bakker
on 2023/06/05 16:03
on 2023/06/05 16: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 - 271 -SecureShip1 +199 - Home Improvements - Content
-
... ... @@ -1,22 +1,20 @@ 1 - Thisreleaseincludesimprovementsto ourcertificaterotation mechanismthataffect all customersusingour eventstreamingoffering. On top of that, new**[[environmenttemplates>>Main.ReleaseInformation.Cloud Templates.WebHome||target="blank"]]**arereleased.Furthermore, additionalaccelerantsfor all integrationdevelopersarehere. This includes improvementsinhow weassistusersinDesign,Create,and Deploy.1 +In the last sprint cycle we have focused on improving various aspects of the portal functionality. Among others we focused on the next-generation architecture, the store, security and certificate management. 2 2 3 -Please find out more on our [[Release blog>> doc:Main.Release Information.Release Blogs.271 -SecureShip.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.WebHome||target= "blank"]]. 4 4 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) 5 +=====Minor changes===== 7 7 8 -==== Minor Changes ==== 7 +* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately 3 months before the expiration dates of event streaming users' access certificates. 8 +* Deploy - Release: After successful machine deployments, unused runtime images will be automatically removed. This can be disabled by changing the machine step in your deployment plan. 9 +* Manage - Monitoring: HTTP statistics page now displays all of the resources. 10 +* Manage - Alerting: congestion control wil be enabled by default with 10 alerts per 10 minutes and user cannot see or change it. 11 +* General - Infra: Changed the library used for storing metadata in the eMagiz Control Tower. 9 9 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) 13 +====Bug fixes==== 13 13 15 +* Create - Store: Spring Reserved words that contain * are not incorrectly replaced with the prefix of the flow. 16 +* Manage - Monitoring: When an application failed to start, not all log messages were visible in the manage phase. 14 14 15 -==== Bug fixes====18 +====Remarks==== 16 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) 20 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.