Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 290.1
edited by Carlijn Kokkeler
on 2024/08/12 12:00
Change comment: There is no comment for this version
To version 200.1
edited by Carlijn Kokkeler
on 2024/02/16 12:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -227 - Fix Frenzy
1 +214 - System Symphony
Content
... ... @@ -1,17 +1,21 @@
1 -During our recent sprint cycle, we have ......
1 +In the last sprint cycle, we focused on improving failover aspects. Moreover, we improved the history of monitoring graphs, it is now possible to view data from up to the last thirty days. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
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.214 - System Symphony||target="blank"]].
4 4  
5 -====Minor changes====
6 -* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview.
5 +=====New features=====
7 7  
7 +* Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once. (#1141)
8 +* Deploy - Architecture: We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
9 +
10 +=====Minor changes=====
11 +
12 +* Deploy - Releases: Deletion of releases with deployed container versions will not be blocked anymore. (#1216)
13 +* Manage - Monitoring: New functionality to ensure that the monitoring graphs in Manage can show data from the last thirty days.
14 +
8 8  ====Bug fixes====
9 -* Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking.
10 -* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
11 -* 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.
12 -* 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.
13 -* Deploy - Releases: When moving to the Deploy phase for the first time, a background action could fail, preventing deploying a release
14 -* Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version.
15 -* 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.
16 -* 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.
17 -* 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.
16 +
17 +* Create - Flow Designer: The help text of the Group attribute has been improved.
18 +* Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test. (#802)
19 +* Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed.
20 +
21 +