218 - Sprightly Spring

In the last sprint cycle, we focused on releasing a major version of our current runtime base image for all our clients running on the current runtime architecture. Please refer to our new runtime image and Spring 6 migration path for more information. Apart from this, we have improved event streaming logging, such that these logs are not cluttered with irrelevant information anymore. Moreover, we have removed the deprecated cloud option 'Root' from the portal.

Please find out more on our Release blog.

New features

• Create - Flow Designer: Copy to clipboard buttons have been added to various pages.
• Deploy - Releases: Copy to clipboard buttons have been added to various pages.
• Deploy - Architecture: For our current runtime architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note that only H2 databases that are registered under the standard eMagiz data folder will be removed. Moreover, it is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. Lastly, for on-premise runtimes, only a reset of the runtime is needed. To use this new functionality, new Cloud Templates are available in our current runtime architecture for single and double environments. Please check out the cloud template release notes for more information.
• Manage - Alerting: The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger.

Bug fixes

• Deploy - Runtime Overview: The runtime overview has been improved with respect to checks on the runtime version. (#1243)