Skip to Content

Changes for page 233 - Policy Polish

Last modified by Carlijn Kokkeler on 2024/11/06 14:06
From version 301.1
edited by Carlijn Kokkeler
on 2024/08/14 09:16
Change comment: There is no comment for this version
To version 311.1
edited by Erik Bakker
on 2024/09/09 09:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -227 - Fix Frenzy
1 +229 - Xpath Alignment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,20 +1,10 @@
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.
1 +During our recent sprint cycle, we have done several improvements to keep our model running smoothly. Moreover, we have made some small changes to various XPath related parts of the portal. Please find out all our changes & bug fixes below.
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.229 - XPath Alignment||target="blank"]].
4 4  
5 5  ====Minor changes====
6 -* Create - Flow Testing: Tracing errors in flow testing has been improved.
7 -* Deploy - Architecture: It is now possible 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 +* Deploy - Deployment plan: We updated the deployment step that temporary disables the triggers in your model. As a result you now have the ability to define after which waiting period (determined in minutes) you want eMagiz to take action. When it reaches this point, eMagiz will act according to the selected option. You can opt to "automatically re-enable triggers", "receive a notification mail", or "both". On top of that we reintroduced the automatic "enable trigger" step that can be added as the last step of your deployment plan to automatically re-enable triggers. Be aware that you *still* need to enable triggers manually if you have manually disabled them prior to deploying. This can be done via the Manage phase.
9 9  
10 10  ====Bug fixes====
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.
9 +* Create - Flow Designer: Improved the helptext of the edit/new header menu in the XPath header enricher component (#727)
10 +* Create - Transformation: Fixed bug that causes the value input field to disappear if you switch from custom xpath to if exists. (#1010)