Wiki source code of 172 - Automation Activation
Last modified by Carlijn Kokkeler on 2024/05/22 13:49
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
7.1 | 1 | Release that introduces a visual refresh on the Capture widget. In addition, this release includes several other improvements and tackles some minor issues. |
| |
1.1 | 2 | |
| |
3.1 | 3 | To benefit from the improvements, please make sure to clear your browser cache (Ctrl+Shift+Del) before signing in the first time. |
| |
1.1 | 4 | |
| |
8.1 | 5 | Find out more in our [[Release blog>>Main.Release Information.Release Blogs.172 - Automation Activation.WebHome||target="blank"]]. |
| |
1.1 | 6 | |
| |
10.1 | 7 | ==== New features ==== |
| |
7.1 | 8 | |
| 9 | * Built-in support for EDI messages | ||
| 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 | ** 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 | |||
| |
10.1 | 13 | ==== Minor Changes ==== |
| |
1.1 | 14 | |
| |
7.1 | 15 | * Deploy - Releases: Improved performance for deploying releases using the deployment plan. |
| 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. | ||
| 17 | * Design - System Message Definition: Importing message definitions from store with multiple namespaces is supported. | ||
| 18 | * Deploy - Releases. You are now able to prevent releases to be deleted (either by eMagiz or manually) by enabling the block autodeletion feature per release. This can be done for at most 3 releases in total. (#587) | ||
| 19 | * Create - Flow designer: Improved the help texts of HTTP outbound components to clarify the exact working of the ‘encoding mode’ setting. | ||
| |
1.1 | 20 | |
| 21 | |||
| |
10.1 | 22 | ==== Bug Fixes ==== |
| |
1.1 | 23 | |
| |
7.1 | 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 | * Community - Q&A: The richtext editor no longer adds a break line when you change a style of text. | ||
| 26 | * Create - Transformation: Fixed the position of the ‘View XSLT Button’ that in some cases was not correct. | ||
| 27 | * Manage - Dashboard: The popup with detailed information on errors did not work for certain types of errors. (#583) | ||
| 28 | * Deploy - Releases: You will not see an error in “Outdated Flows” pop-up if your release has outdated flows. | ||
| 29 | * The help text is appearing correctly when clicking attributes on a page. | ||
| |
1.1 | 30 |