Changes for page 172 - Automation Activation
Last modified by Carlijn Kokkeler on 2024/05/22 13:49
From version 9.1
edited by Erik Bakker
on 2022/09/02 09:50
on 2022/09/02 09:50
Change comment:
There is no comment for this version
To version 10.1
edited by Carlijn Kokkeler
on 2024/05/22 13:49
on 2024/05/22 13:49
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -4,13 +4,13 @@ 4 4 5 5 Find out more in our [[Release blog>>Main.Release Information.Release Blogs.172 - Automation Activation.WebHome||target="blank"]]. 6 6 7 -==== =New features =====7 +==== New features ==== 8 8 9 9 * Built-in support for EDI messages 10 10 ** Design - System: EDI is a new message format supported in eMagiz. You can select this as the default option when editing a system or when editing a system message. Note that, this option is supported only for Generation 3 runtimes. 11 11 ** Create - Flow designer: The autogenerated definitions and transformations components are customized so that EDI to XML validations and transformations are possible. Note that in this version the filter will not work with the eMagiz message definitions if they use multiple namespaces, in that case, a custom XSD should be used. 12 12 13 -==== =Minor Changes =====13 +==== Minor Changes ==== 14 14 15 15 * Deploy - Releases: Improved performance for deploying releases using the deployment plan. 16 16 * Capture - Requirements Designer: The requirements designer got a visual refresh. Furthermore, new (multi-tenant) systems can now be created by clicking the blue rectangles in the left panel, rather than by dragging them in. ... ... @@ -19,7 +19,7 @@ 19 19 * Create - Flow designer: Improved the help texts of HTTP outbound components to clarify the exact working of the ‘encoding mode’ setting. 20 20 21 21 22 -==== =Bug Fixes =====22 +==== Bug Fixes ==== 23 23 24 24 * Deploy - Releases: We fix a small issue that adds an onramp (or an offramp) that is linked to an exit/entry connector to a release at a later moment. (#442) 25 25 * Community - Q&A: The richtext editor no longer adds a break line when you change a style of text.