Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 12.1
edited by Erik Bakker
on 2022/10/24 12:01
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 -186 - Daemon Switch
1 +229 - Xpath Alignment
Content
... ... @@ -1,25 +1,10 @@
1 -Release that brings the new monitoring stack to fruition and brings various updates to handling multiple namespaces. On top of that, we have released a sleuth of smaller feedback items and 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.186 - Daemon Switch.WebHome||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 -* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file.
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.
7 7  
8 -=====Minor changes=====
9 -
10 -* Design System. Changed the look and feel across the portal altogether. Changes can be seen in:
11 - ** Datagids, where there is now on hover action for example.
12 - ** Pop ups
13 - ** Context menus, also have on hover action
14 - ** Styling of scrollbars
15 - ** Warning, info and error context labels.
16 -* Message Redelivery - admin logs improved to better analyze issues when they occur
17 -* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality
18 -* Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed
19 -
20 20  ====Bug fixes====
21 -* Deploy - Deployment plan. Performance of page to deploy a release increased significantly
22 -* Store - Import resources was incorrectly done in specific cases, which is now fixed
23 -* Store - Target namespace will be imported when importing an XML Message Definition
24 -* Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model.
25 -* Store - Importing items from the store sometimes resulted in invalid JMS connection factories.
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)