206 - Situational Deployment

In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.

Please find out more on our Release blog.

Minor changes

• Design - Framework: The framework used in the flow designer has been updated to the latest version.
• Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier.
• Design - Store: We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
• Create - SSL: Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
• Deploy - Architecture: The title of the'apply to environment' action for changing topic retention size has been changed to be less confusing.
• Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum.
• Deploy - Deployment plan: A change in the memory settings of the JMS triggers a redeployment of the container.
• Deploy - Logging: New logging feature enabling us to make better choices in deprecating old encryption standards.
• Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
• Deploy - Release properties: The description of a property can be changed by editing the property.
• Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
• Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
• Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
• Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment.
• Manage - Alerting: Inactivated users should be removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
• Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes.
• Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default.
• Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
• Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform of the action.
• Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.

Bug fixes

• Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
• Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
• Design - Store: We fixed an issue that static copies were missing when importing store items.
• Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
• Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release.
• Manage - Monitoring: It is now possible to search on messages partially in Manage Monitoring.
• Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.

Infra and image changes

• No infra and/or image changes is this release.