208 - Controlled State

In the last sprint cycle, we focused on providing users with a monitoring functionality for the state generation components. On top of that, we also made several improvements to the components interfacing the users to improve the user experience aspect of our platform. Moreover, we made some bug fixes and improvements on releases in Deploy and monitoring in Manage.

Please find out more on our Release blog.

Minor changes

• Create - Flow Designer: Input fields for XPath expressions have been made wider and capable of expanding to facilitate longer inputs. (#822)
• Create - Flow Designer: Small styling changes and bug fixes have been implemented for edge cases during editing channels in the Flow Designer.
• Deploy - Releases: During removing a release, users will be informed about the environments and the runtimes in which the release under deletion is running. (#1060)
• Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
• Deploy - Deployment: The “preparing” step of the release at the beginning of the deployment is now faster due to the improved process of building the images.
• Manage - Monitoring: There is a new page called "State generation statistics" that is located right under the Topic statistics navigation menu, which is only shown and accessible for models that have the add-on license for state generation.
• Manage - Error messages & Log entries: Searching on entries in the next-generation architecture models now supports phrase matching, meaning that users can search entries based on phrases containing two or more words and entries with distances of 2 or incomplete search phrases.
• Manage - Alerting: In Alerts, the previous "Source" column is renamed to "Source trigger" and its value is derived from the type of trigger which generates alert.
• All - Toggles: We updated all instances of the toggle switch in the platform due to the latest eMagiz Design System module implementation in our platform.
• All - Error Channel: Added a migration step in Gen3 migration, we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.

Bug fixes

• Deploy - Deployment: We fixed an issue that the deployment plan got stuck or stopped randomly sometimes.
• Deploy - Deployment: We resolved an issue where sometimes older containers get deployed, while eMagiz shows the new containers are deployed.
• Manage - Monitoring: Improved message processing in infra components that should reduce the occurrence of log messages failing to be sent in Gen3 models.