202 - New Equilibrium

In the last sprint cycle, we focused on finishing our work on the release properties functionality introduced in this release. On top of that, we have some additional smaller feedback items and bug fixes coming out of the Hackathon for you.

Please find out more on our Release blog.

New features

• Deploy - Releases: We removed two unnecessary release options: “Set release properties” and “Check properties. “ You can quickly update your properties via the Release properties overview.
• Deploy - Releases: Before activating or deploying a new release, you should fill in all properties that relate to your deployment. If there are any properties without value, we will show them to you. Then you can update them and continue your deployment.
• Deploy - Properties: This tab 'Properties' for managing properties is deprecated as of Release 202. As a result, it cannot be used anymore to manage properties. You can manage your properties via the 'Releases' overview. On this overview, you can select the wrench icon on the 'Create phase release' to find the property management overview. For more information about the management of properties and the related features, click on the right-bottom corner on 'Help and check out our documentation.
• Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture to host a MQTT broker in a failover (i.e., double lane) architecture. Please check out the cloud template release notes for more information.

Minor changes

• Store - Export: "Store exporter" users can test their exported store items immediately without waiting for approval. (#1001)
• Deploy - Releases: The infographic has been updated.
• Deploy - Release Properties: Required properties are checked if they contain nested properties and are not missing values.
• Deploy - Property release: Names of properties can be created/removed/edited.
• Deploy - History: We deprecated the old page History, which displays the property changes in your model. The properties' history is on the Deploy phase's History page.
• Deploy - Architecture: Changes made to AWS Slot settings are recorded in history. (#966)
• Manage - Monitoring: Improved performance of 3rd generation runtime dashboards.

Bug fixes

• Design - Import: Import into design from the store is possible, even if the integration is not in Create yet.
• Create - Flow Designer: Improved validation on XPath header enricher. (#1005)
• Create - Flow Designer: We fixed an issue that your flow fragment metadata disappeared when you canceled your changes of the existing flow fragment in your new version of the store item. (#989)
• Create - Flow Designer: In some cases, when copying/pasting components into a flow, validation alerts would be displayed that did not belong to a component. This problem is now fixed. (#955)
• Create - Flow Designer: We fixed an issue that prevents dragging and dropping an annotation from the left panel after a search from the search box. The speed of creating the dialog to enter the component’s name is also improved.
• Create - Flow Testing: Properties will not disappear from the list when canceling changes on a default property value. (#913)
• Create - Flow Testing: Users with view rights can edit test case names, descriptions, and property values. (#973)
• Deploy - Architecture: The runtimes will display the number of connected flows, not "Zero."
• Deploy - Architecture (Runtime Settings): Moved the delete button to the right side of the page and fixed the bug in the help text.
• Deploy - Releases: We fixed an issue that prevented you from seeing a comparison message when hovering over an exit gate flow of the API pattern if you compare two release versions in Deploy. (#839)
• Deploy - Releases: We improved the loading buttons of releases on the right pane by Order (Ascending).

Infra and image changes

• Runtime Image - Next-Generation Double Lane: A new runtime image is released including a Java version update. Please check out the runtime images release notes for more information.
• Infrastructure: Tightened security policies for a more secure infrastructure.