Skip to Content

241 - Wild West

Last modified by Erik Bakker on 2025/03/27 09:08

In the last sprint, we have released a lot in terms of usability improvements while working within the various phases of eMagiz and when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new runtime image containing a much-needed improvement regarding deployment executions when working with state generation and code mappings on top of various improvements in our underlying code.

Please find out more on our Release blog.

New Features

  • Deploy - Releases: A comparison feature for the Deploy phase is added. The comparison feature allows users to compare releases to track the differences in property values of those releases. The feature also provides information on who made the changes. The differences are categorized by “InRelease” and “NotInRelease,” which means that the additional property value is either in the first selected release (InRelease) or the second selected release (NotInRelease).
    • This functionality only works for releases created after this release.

Minor Changes

  • Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471)
  • Capture - Add Integration: Removed the ‘remarks’ field from the ‘New Integration’ screen in Capture because this field was not visible enough in the rest of the portal. (#1608)
  • Capture / Design: For new systems, message types, machines, tenants, and models, hyphens are no longer allowed in the technical name. The technical name can only consist of lowercase letters and digits and must start with a letter. This also applies to systems, message types, and tenants that have not yet been transferred from design to creation. The portal will give an error message while transferring, and the hyphen has to be removed manually.
  • Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554)
  • Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616)
  • Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure.
  • Infra - Security: Improved security by implementing additional safeguards for AWS native services.

Bug fixes

  • Capture - Add System: A loading bar is displayed before showing the pop-up when a user tries to create or edit a system. (#1228)
  • Capture - Edit System: When editing a system, the validation now considers that the name cannot be an empty string. (#1562)
  • Design - Message Definition: Two minor improvements are introduced:
    • The widget prevents users from adding the same message attribute within a message definition multiple times. 
    • When adding a new message entity within your message definition and expanding the existing message definition, it doesn’t throw an exception when the user presses the Save button multiple times in a short time frame.
  • Design - Catalog: When creating the Swagger JSON, all custom examples users add will be shown correctly when displaying the Swagger. (#1597)
  • Design - Solution Architecture: When modifying the number of runtimes of a system, the validation will now take into account that the value may not be empty (#1513)
  • Create - Add Integrations: Users can untransfer a flow even when there is a property attached to the flow. (#1590)
  • Create - Add Integrations: When an integration is transferred from the Create phase, the flow, flow versions, and the corresponding integration in the Deploy phase are cleaned.
  • Create - Components: The browser page now displays the correct page title (#1509)
  • Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549)
  • Create - Flow Designer: The default name of the REST template support object generated in passthrough API gateway operations now matches the (technical) name of the integration. (#1560)
  • Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already an existing property description. (#1526)
  • Deploy - Environment Template: Fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly.
  • Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore moves the user to the queue browser of the correct environment. (#1408)
  • Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents flows using code mappings from encountering errors when stopping their runtime while messages are still being processed. (#1550)

Remarks

  • New eMagiz Connector for Queues: The new eMagiz connector has been tested in Mendix with Java 21, and functionality works as expected.