Skip to Content

Changes for page eMagiz Runtime - 5.0.3

Last modified by Erik Bakker on 2022/06/16 13:33
From version 11.1
edited by Erik Bakker
on 2022/06/16 13:33
Change comment: There is no comment for this version
To version 7.1
edited by Erik Bakker
on 2022/06/16 12:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -eMagiz Runtime - 5.0.3
1 +Automation Activation
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.Release Information.Runtime.WebHome
1 +Main.Release Information.Portal.WebHome
Content
... ... @@ -1,12 +1,31 @@
1 -Third maintenance release in the eMagiz 5.0.x line. This release fixes several startup and shutdown related issues.
1 +Release that introduces a visual refresh on the Capture widget. In addition, this release includes several other improvements and tackles some minor issues.
2 2  
3 +To benefit from the improvements, please make sure to clear your browser cache (Ctrl+Shift+Del) before signing in the first time.
3 3  
4 -===== Bug Fixes =====
5 +Find out more in our [release blog]
5 5  
6 -* The lock file is now stored in the data directory. This enables proper EFS locking in the AWS cloud.
7 -* A datadir revision file is introduced. This can be used to identify differences between (versions of) data directories and the runtimes using it.
8 -* Fixed the issue where, in specific cases, having two versions of the same flow might cause auto-startup to skip starting of the flow altogether. This was especially problematic if the flow in question was the infra flow, making it impossible to control the runtime from the iPaaS portal.
9 -* Fixed clearing of auto-started flows, when the runtime was given the shutdown command immediately after starting. This should solve a rare issue where after a restart the runtime would not start any flows, making it impossible to control the runtime from the iPaaS portal.
10 -* The startup process of the runtime will now stop when the runtime is given the shutdown command. Previously, the startup process would still continue when attempting a shutdown during startup, resulting in unexpected behaviour.
11 11  
8 +===== New features =====
12 12  
10 +* Built-in support for EDI messages
11 + ** 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.
12 + ** 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.
13 +
14 +===== Minor Changes =====
15 +
16 +* Deploy - Releases: Improved performance for deploying releases using the deployment plan.
17 +* 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.
18 +* Design - System Message Definition: Importing message definitions from store with multiple namespaces is supported.
19 +* 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)
20 +* Create - Flow designer: Improved the help texts of HTTP outbound components to clarify the exact working of the ‘encoding mode’ setting.
21 +
22 +
23 +===== Bug Fixes =====
24 +
25 +* 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)
26 +* Community - Q&A: The richtext editor no longer adds a break line when you change a style of text.
27 +* Create - Transformation: Fixed the position of the ‘View XSLT Button’ that in some cases was not correct.
28 +* Manage - Dashboard: The popup with detailed information on errors did not work for certain types of errors. (#583)
29 +* Deploy - Releases: You will not see an error in “Outdated Flows” pop-up if your release has outdated flows.
30 +* The help text is appearing correctly when clicking attributes on a page.
31 +