Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 295.1
edited by Carlijn Kokkeler
on 2024/08/12 12:27
Change comment: There is no comment for this version
To version 112.1
edited by Carlijn Kokkeler
on 2023/10/11 12:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -227 - Fix Frenzy
1 +206 - Situational Deployment
Content
... ... @@ -1,19 +1,26 @@
1 -During our recent sprint cycle, we have done many fixes. These are mainly related to flow testing, alerting, and the deploy phase. Apart from that, we have improved the tracing information for errorChannel messages, and added search functionality to the Start/Stop flows overview.
1 +In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.227 - Fix Frenzy||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Situational Deployment.WebHome||target="blank"]].
4 4  
5 -====Minor changes====
6 -* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
7 -* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview. (#1311)
5 +=====New features=====
8 8  
7 +* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
8 +
9 +=====Minor changes=====
10 +
11 +* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration.
12 +* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869)
13 +* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1042) (#1046) (#1052)
14 +
15 +
9 9  ====Bug fixes====
10 -* Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking. (#1294)
11 -* Create - Flow Testing: The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
12 -* Create - Flow Testing: In case opening a log of test execution is not possible, a warning message will now be shown.
13 -* Create - Message Definitions: The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes to your namespaces in your message definitions.
14 -* Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted. (#1379)
15 -* Deploy - Releases: When moving to the Deploy phase for the first time, a background action could fail, preventing deploying a release. This has been resolved.
16 -* Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version. (#1310)
17 -* Manage - Alerting: We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture. You will be able to test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
18 -* Manage - Alerting: You can now add internal and external recipients to your default trigger configuration at the same time, and they will be applied to your triggers correctly.
19 -* Manage - Alerting: We have fixed a case where a tenant-queue-trigger could be activated on a hybrid environment, before the JMS of that environment had been deployed to the current runtime.
17 +
18 +* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054)
19 +* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.
20 +* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed.
21 +* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
22 +
23 +
24 +=====Infra and image changes=====
25 +
26 +* No infra and/or image changes is this release.