Skip to Content

Changes for page 169 - Check, Act

Last modified by Carlijn Kokkeler on 2024/05/22 13:50
From version 7.1
edited by Erik Bakker
on 2022/06/16 12:15
Change comment: There is no comment for this version
To version 14.1
edited by Carlijn Kokkeler
on 2024/05/22 13:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Automation Activation
1 +169 - Check, Act
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,31 +1,31 @@
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 +The Check, Act release introduces version 10.37.0 of eMagiz portal. This release brings an improved error check in Design and Create phase and from now on, new API gateways will run on the latest generation (Gen3) runtime by default.
2 +In addition, this release includes several other improvements and tackles some minor issues.
2 2  
3 3  To benefit from the improvements, please make sure to clear your browser cache (Ctrl+Shift+Del) before signing in the first time.
4 4  
5 -Find out more in our [release blog]
6 +Find out more in our [[Release blog>>Main.Release Information.Release Blogs.169 - Check, Act.WebHome||target="blank"]].
6 6  
7 7  
8 -===== New features =====
9 +==== Major Changes ====
9 9  
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.
11 +* Design - Architecture: Gateway containers are running on Gen3 by default if the model has just received the API license.
12 +* Errors check in the Design and Create phase that will help you to find which step you have forgotten when building an integration.
13 + ** Design - Solution Designer: Errors in mappings, and missing technical names for systems, tenants and API operations are now shown in the solution designer. Additionally, the right panel has been redesigned with a new UI and the ability to show/hide tasks on the canvas and in the right panel.
14 + ** Create - Overview: Errors in transformations are now shown in the create overview. Errors in transformations can be hidden from the canvas in the transformation tooling by clicking the hide icon on the error. Additionally, the right panel has been redesigned with a new UI and the ability to show/hide tasks on the canvas and in the right panel.
13 13  
14 -===== Minor Changes =====
16 +==== Minor Changes ====
15 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.
18 +* Create - Flow testing: The message comparison screen has been reorganized to optimize space by only showing headers when the expected and actual values differ from each other. All headers are still shown on the details pop-up screen. This pop-up has also increased his size and headers and the payload are grouped in 2 separate tabs. (#483)
19 +* Create - Flow Testing: When running a test case that has properties defined on the flow, a warning pop-up will appear asking you to fill in the values in case they are empty.
21 21  
22 22  
23 -===== Bug Fixes =====
22 +==== Bug Fixes ====
24 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 -
24 +* Design - Store: When importing a system message from Store into system message, there will be no error popup.
25 +* Create - Store: When overwiting a version of a substore item, the wildcard versions (e.g. 1.3.*) will be hidden in the list of available versions.
26 +* Create - Flow testing: Test messages based on message definitions can be autogenerated for event processors. (#447)
27 +* Capture - Add integration: You can add an API integration and it will have a unique technical name automatically as well as an unused operation for the path corresponding to the selected message type.
28 +* Design - Open API specification: Improved generation of the the Open API specification. To benefit from this, please trigger the recreation of the file.
29 +* Create - Resources: You can change the file of a resource used in a flow without encountering errors such as 'Failed to commit'.
30 +* Deploy - Architecture: Improved functionality of waking up a cloud slot so that no strange errors occur.
31 +* Manage - Error messages: XML Validation errors are available for inspection when opening a certain error message. (#330)