192 - Small Step

Last modified by Erik Bakker on 2023/06/15 11:59

The release introduces two new features for our 3rd generation runtime. Subsequently, we will release several minor feedback points and bug fixes.

Please find out more on our Release blog.

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.
Manage - Monitoring: New dashboard, ‘Event streaming statistics,’ is available for you to monitor your topics and consumer groups.

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.
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.
Deploy- User Management: Transfer from design button imports users and roles (#562)
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.

Create - Flow Designer: We applied a new settings 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 which take too long to read. For this to be applied please reset your jms flow and deploy the new version on your bus.
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.
Deploy/Monitoring - Debugger: Pressing the "Stop debugger" button now functions correctly

Navigation