Changes for page 271 - Secure Ship
Last modified by Erik Bakker on 2026/06/29 09:20
From 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
To version 343.1
edited by Erik Bakker
on 2026/06/29 09:20
on 2026/06/29 09:20
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 - 192 - SmallStep1 +271 - Secure Ship - Content
-
... ... @@ -1,29 +1,23 @@ 1 -Th erelease introduces twonewfeatures for our3rd generation runtime.Subsequently,wewill releaseseveralminorfeedbackpointsandbugfixes.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. 192 - SmallStep.WebHome||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===== 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. 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 -==== =Majorchanges=====8 +==== Minor Changes ==== 10 10 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. 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. (#1792) 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 in line with our best practices. (#1768) 12 12 13 -=====Minor changes===== 14 14 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. 15 +==== Bug fixes ==== 19 19 17 +* Capture - Delete System: When being prevented from deleting a system by eMagiz, you no longer are confronted with an everlasting platypus. (#1771) 18 +* Deploy - System: We fixed an issue that, on some occasions, the wrong file location is set for the H2 database if the runtime runs on an on-premises machine. 19 +* Deploy - User Management: We fixed inconsistent errors in Deploy - User Management overview, making it more reliable to manage users and their credentials. 20 20 21 -==== Bugfixes====21 +==== Remarks ==== 22 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 - 23 +* Support employees can trigger a rollback on the intermediate certificate on the customer authorization server.