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 49.1
edited by Erik Bakker
on 2023/02/16 08:49
on 2023/02/16 08:49
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 +192 - Small Step - Content
-
... ... @@ -1,22 +1,29 @@ 1 -Th isrelease includes improvements toour certificaterotation mechanismthat affect all customersusingourevent streaming offering. On top of that,new**[[environmenttemplates>>Main.ReleaseInformation.CloudTemplates.WebHome||target="blank"]]**arereleased.Furthermore, additional accelerants for allintegration developersarehere. This includesimprovementsinhow we assistusersin Design, Create, and Deploy.1 +The release introduces two new features for our 3rd generation runtime. Subsequently, we will release several minor feedback points and bug fixes. 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.192 - Small Step.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 +=====New features===== 6 +* Deploy - Architecture: We add a new option per container to open a page that you can use a feature "Start / Stop flows" for runtime running on the 3rd generation runtime. Note that the debugger functionality can also be started on this view. 7 +* Manage - Monitoring: New dashboard, ‘Event streaming statistics,’ is available for you to monitor your topics and consumer groups. 7 7 8 -==== MinorChanges====9 +=====Major changes===== 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) 11 +* Create - Flow Designer: We applied a new setting for the JMS flow where the JMS flow will try to shrink the journal files to 50, so it does not end up with a high amount of JMS files that take too long to read. For this to be applied, please reset your JMS flow and deploy the new version on your model. 13 13 13 +=====Minor changes===== 14 14 15 -==== Bug fixes ==== 15 +* Design- Kafka topic: As a user, you can now only define the retention size on the topic level. Based on that input value and a set of best practices eMagiz will, in turn, calculate the correct settings for you. Don't hesitate to contact your partner manager if you want to change the default settings. When applying the configured settings to your topic, we also send configuration settings for segment bytes and segment ms based on our best practice to improve performance. 16 +* Create - Flow Designer: You can make a multiple selection zone by pressing and holding the left mouse button instead of pressing the "Shift" key from now on. 17 +* Deploy- User Management: Transfer from design button imports users and roles 18 +* Deploy - Release: We improved the activation process of a release with one or more 3rd generation runtimes. As of now, we are preparing the release as the first step of deploying your release. In this overview, you can see the progress of the preparation step when you execute the deployment of a release. Note that a new deployment plan is needed to make this work. 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 + 21 +====Bug fixes==== 22 + 23 +* Deploy/Monitoring - Debugger: We have improved the error handling on the debugger functionality to ensure it does not show the error code and technical error anymore. 24 +* Deploy/Monitoring - Debugger: Pressing the "Stop debugger" button now functions correctly 25 + 26 +====Remarks==== 27 + 28 +* Mendix Runtime has been upgraded to Mendix 9.22.0. 29 +