222 - Flee Frustration

In the last sprint cycle, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Find out about the rest below! 

Please find out more on our Release blog.

New features

• Design - Architecture: If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.

Bug fixes

• Design - Architecture: The number on the JMS container correctly displays the amount of queues present in Design. (#1284)
• Create - Flow Designer: Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. (#1053)
• Deploy - Architecture: We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. (#1282)
• Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. (#1293)
• Deploy - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
• Deploy - Releases: Users are blocked from deploying at the same time on the same environment on the current runtime architecture. (#1293)