Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 240.1
edited by Carlijn Kokkeler
on 2024/05/06 14:06
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 -220 - Patch Parade
1 +229 - Xpath Alignment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,14 +1,10 @@
1 -In the last sprint cycle, we have worked on a new runtime image LINK that contains a fix for an issue regarding SFTP sessions. Furthermore, we did several small improvements and many bug fixes.
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.220 - Patch Parade||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.229 - XPath Alignment||target="blank"]].
4 4  
5 -===== New features =====
6 -* Capture - Integrations: Information about the integration pattern of a selected message type has been added to the new integration pop-up. (#1214)
7 -* Create - Flow designer: A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
8 -* Deploy - Releases: Search boxes in the properties overview are now shown by default. (#1325)
9 -* Manage - History: All events that relate to message queues (delete message, delete all messages or delete queue) are now logged in the Manage phase instead of the Deploy phase. (#1278)
5 +====Minor changes====
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.
10 10  
11 -
12 -===== Bug fixes =====
13 -* Design - Message mapping: It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. (#1179)
14 -* Create - Flow designer: It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. (#852)
8 +====Bug fixes====
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)