Changes for page 233 - Policy Polish

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-232 - Bug Busters
	1	+229 - Xpath Alignment

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.CarlijnKokkeler
	1	+XWiki.ebakker

Content

...	...	@@ -1,22 +1,10 @@
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, as well as pop-ups and search functionalities. Find out all below!
	1	+During our recent sprint cycle, we made several improvements to keep our model running smoothly. We also made some small changes to various XPath-related parts of the portal and updated our deployment plan. Please find all our changes and bug fixes below.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.232 - Bug Busters||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.229 - Xpath Alignment||target="blank"]].
4	4
5		-
6	6	====Minor changes====
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)
	6	+* Deploy - Deployment plan: We updated the deployment step that temporarily disables the triggers in your model. As a result, you can now 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, which 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 before deploying. This can be done via the Manage phase.
8	8
9		-
10	10	====Bug fixes====
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		-* Design - CDM: When editing a relation in a datamodel, you are now prevented from breaking the relation. (#1465)
14		-* Create - Flow Designer: The tooltip in the Flow Designer now zooms in/out correctly. (#1496)
15		-* 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)
16		-* Create - Transformation: Source filters will now display the attribute filter statement correctly. (#1353)
17		-* 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)
18		-* Deploy - Containers: The 'Delete' button in the Containers overview is no longer visible for users without the required permissions. (#1464)
19		-* 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)
20		-* 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)
21		-* 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)
22		-* All: Integrations ans systems are now sorted in the same way across all phases. (#1344)
	9	+* Create - Flow Designer: Improved the help text 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 it exists. (#1010)