We planned for Q2 deployment updates to have small QoL fixes. The key-users expressed they wanted to try updating after every small fix instead of one big update. We wanted to try this to see how big the overhead is vs how quick you get access to new functionality.
In the last 2 weeks 3 updates have been done. Since they were really small, they took no downtime. The parties that were involved in requesting the QoL updates got notifications, but otherwise communication has been only in the deployment application using the main metro tile. Did you know you can click the tile to see the notes?
Changes that have been made:
-
Support for 3.9 rollout: We found a bug that made it hard to change the generator main version in the order. The decision was made that for parts of an order, the ordersettings would be leading and stand-alone integrations / generations / installations would still have the same functionality.
-
There was a feature request to sort the framework and generator versions descending instead of ascending. We made every dropdown concerning a version sort descending and only show active versions.
-
There was confusion over the installationstatus. It turned out that that was never shown and the status at the workflow panel was treated as an installation status, while it was a workflow status. This has been addressed by renaming the workflow status field to workflow status and include the installation status in the page title.
-
We fixed a bug for the quick access buttons where it would show an error instead of creating a new installation.
-
An SR asked for a remarks field for the custom web.config settings. This has been implemented as a manual field only, as a reminder to yourself as why you set this setting.
If you have more small QoL improvements, please create an SR.