Changes for page 232 - Bug Busters

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-229 - Xpath Alignment
	1	+188 - Close Encounters

Content

...	...	@@ -1,10 +1,25 @@
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	+The release brings several improvements to our 3rd generation runtime and the interaction with it. On top of that, we have several feedback items and bug fixes.
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.188 - Close Encounters.WebHome||target="blank"]].
4	4
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.
	5	+=====New features=====
	6	+* Design - Store: It is now possible to import Transformations and Data Models from the store into a model.
	7	+** The Design Store can also be opened from the Mapping and Data Model screens.
	8	+** The Design Store now offers search options for store items, including Transformations and Data Models.
	9	+** When importing a Store item with a Transformation or Data Model, a new merge tool is available to link the Store Items data model to the users' data model or to add new attributes/entities to the user data model.
	10	+** When importing a Store item with a data model that has been previously linked, the links are automatically restored, allowing for easy updating of store-based Integrations and easier installation of multiple Store items with the same data model.
7	7
	12	+=====Minor changes=====
	13	+
	14	+* Create - Flow Designer: Code mapping is now available for models migrating to the 3rd generation runtime
	15	+* Create - eMagiz Mendix Connector exit: Download buttons are added for non-legacy eMagiz Mendix connectors.
	16	+* Create - Overview: You will now see your errors within a flow but on the Create - Overview. To activate this, open your flow, and the number of errors you have in it, if any, will update so that next time, you don't have to navigate inside the flow to check how many alerts you have.
	17	+
	18	+
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)
	20	+* Design - Store: Importing store items from response messages doesn't cause issues anymore.
	21	+* Design - Store: Importing response messages and transformation to API integration is possible.
	22	+* Design - API Gateway: The order of attributes in gateway messages was sometimes different than in the generated Open API document. (#783)
	23	+* Create - Flow Designer: Ensure that the copy and pasting experience works for all flows.
	24	+* Create - Flow Designer - Store: We fixed the maintaining selection of flow fragments from the store.
	25	+* Manage - Exceptions of error messages: The count of error messages per exception class is now displayed. (#744)