Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 57.1
edited by Erik Bakker
on 2023/03/14 08:31
Change comment: There is no comment for this version
To version 299.1
edited by Carlijn Kokkeler
on 2024/08/14 09:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -194 - Giant Leap
1 +227 - Fix Frenzy
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,24 +1,20 @@
1 -The release introduces various improvements on our 3rd generation runtime architecture and various other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements.
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, added search functionality to the Start/Stop flows overview, and enabled our new queue trigger functionality for redelivery-enabled messaging queues.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.194 - Giant Leap.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.227 - Fix Frenzy||target="blank"]].
4 4  
5 -=====New features=====
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)
8 +* Manage - Alerting: The new queue triggers feature has been updated to be able to handle redelivery-enabled messaging queues.
6 6  
7 -* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V130.WebHome||target="blank"]].
8 -* Design - Settings: We added XML support to API Management. To enable this feature, change the 'Default message format' in the Design settings section. You can change individual operations by changing the message format of your gateway message. Migrating existing operations requires a reset of the exit flow and a change in the catalog in Design. For more information, see the release blog post. (#815)
9 -* Deploy - Releases: New release properties pop-up that shows all properties in your release, grouped by containers that they are assigned to. This pop-up can be accessed by pressing the wrench-shaped icon, which becomes available once a release is set as active.
10 -
11 -=====Minor changes=====
12 -
13 -* Design - API Gateway: OData API type exclusively selectable for system admin. (#816)
14 -* Design - API Catalog: When you change a path in the Design phase, your HTTP inbound gateways that use the changed path will also be updated in Create phase if you have edit rights. (#524)
15 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
16 -* Manage - Error messages: Message history is sorted by timestamp descending.
17 -
18 18  ====Bug fixes====
19 -
20 -* Create - Message Definition: Attribute can be declared as JSON array in API Gateway and Event Streaming. (#908)
21 -* Create - Migration: We fixed a third-generation migration issue where the legacy error handling flow components were not removed from the asynchronous routing flow.
22 -* Create - Flow designer: when migrating a container’s flows from gen2 to gen 3, “global wire tap” components and their relevant components will be removed.
23 -* Deploy - Release: We fixed an issue that caused images not to be built in specific situations when running in the new runtime generation runtime.
24 -* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. (#797)
11 +* Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking. (#1294)
12 +* Create - Flow Testing: The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
13 +* Create - Flow Testing: If opening a test execution log is not possible during flow testing, a warning message will now be displayed.
14 +* 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.
15 +* 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)
16 +* Deploy - Releases: We have resolved a bug that prevented you from deploying anything on a newly created model.
17 +* Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version. (#1310)
18 +* 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.
19 +* 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.
20 +* 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.