Skip to Content

Changes for page 233 - Policy Polish

Last modified by Carlijn Kokkeler on 2024/11/06 14:06
From version 311.1
edited by Erik Bakker
on 2024/09/09 09:52
Change comment: There is no comment for this version
To version 331.1
edited by Carlijn Kokkeler
on 2024/10/21 12:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -229 - Xpath Alignment
1 +232 - TBD
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,10 +1,21 @@
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.
1 +During our recent sprint cycle, We did a hackathon again so we have a lot of bug fixes! The visibility of several buttons has been improved, search functionalities have been improved, and pop-ups have been corrected. Find out all below!
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.229 - XPath Alignment||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.231 - Microscopic Madness||target="blank"]].
4 4  
5 +
5 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 +* Deploy - Releases: When creating a new property name for a new property value, it wil automatically be selected for the new property value. (#1433)
7 7  
9 +
8 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)
11 +* Design - Architecture: It is no longer possible anymore to create machines with the same technical name. (#1457)
12 +* Design - Architecture: When enabling or disabling our failover feature for a system, its connector container will no longer be moved to another machine if not required.
13 +* Create - Flow Designer: The tooltip in the Flow Designer now zooms in/out correctly. (#1496)
14 +* Create - Flow Designer: The conditional visiblity of filtering operations of SMB, SFTP & FTP outbound gateways when using the 'remove' and 'get' operations has been improved. (#1439)
15 +* Create - Transformation: Source filters will now display the attribute filter statement correctly. (#1353)
16 +* Deploy - Architecture: The pop-up that is shown after pressing 'apply to environment' in Deploy Architecture will only show the current changes, irrelevant information has been removed. (#1104)
17 +* Deploy - Containers: The 'Delete' button in the Containers overview is no longer visible for users without the required permissions. (#1464)
18 +* Deploy - Releases: We updated the user rights in a model such that in order to deploy a release in Deploy, you should have both edit rights in Deploy and Manage. (#1495)
19 +* Manage - Code Mappings: When searching in the code mappings overview and pressing enter in a search field, search results would get duplicated. This has been fixed. (#1105)
20 +* Manage - Explore: The 'Explore' button will no longer be hidden if there are no results when searching on a queue name in the queue browser. (#1409)
21 +