Here's our first release of this quarter. Key focus remains on Flow testing, additional results of the Hackathon and API Gateway improvements
Please find out more on our Release blog.
New features
- Create - Flow Testing: so far, the Flow Testing allows test eMagiz flows by defining the testing point on the starts and the end points and comparing the actual and expected messages. In this release, “Live Mode Testing” is introduced, making it possible to test communication with real endpoint. That means that an “http output gateway” can be marked in “Live Mode”, if so, the http output gateway will send its http request to the real endpoint and received the result so we can go further with testing.
- Deploy - Architecture: You can now find the Static IP address of connector machines when you update to the new cloud template.
Minor changes
- Deploy - Architecture: The topics are now ordered alphabetically and the runtimes will now get the same order as design architecture (after ‘apply to environment’)
- Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can not change CDM message definition, Gateway message definition, even Event streaming message definition without the proper right.
- Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran.
- Administration-User management: Company contact can edit permissions of models that fall under child companies
- Administration: Contracts page removed
- Create-Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter.
- Deploy - Releases: We reduced the time it takes to prepare a release, before it can be deployed. The process of building runtime images has been optimized.
- Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
- Design - Store: You are able to see some warning messages when you import a transformation from store. Because your imported transformation is required some information from the related store fragment. You should include that store fragment to avoid a breaking transformation in Create phase after importing. Afterward, we will update your existing flow component transformer to make it work correctly.
- Design - Store: We updated importing to help you avoiding an error during importing store item that will break your message definition in some special cases.
- Create - Store: We excluded automatically resources that are not good enough from the exporting wizard. Then you will easy to recognize a problem and avoid creating unusable store item.
- Flow Designer: Resources in "Unused resources" section can be marked as used for the case that the resources are referred by components through property placeholders or in custom spel expressions.
- Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests, if that parameter was not supplied. Please reset your entry flow to apply the fix.
- Create - API Gateway: We fixed an issue where API-Key secured requests would fail with error code 500 instead of code 401, if no API-Key was supplied. Please reset your entry flow to apply the fix.
- Design - Store: We fixed an issue that you import the message definition(s) and a specialized DataType of imported message definition(s) are not matched with the exported message definition(s). Now, they are matched and your transformation won't get issues.
- Create-Resources: When viewing a resource, its full name will be shown, removing the need to download the resource in order to obtain its name
- Create - Flow designer: Improve responsiveness of resources tab at right panel
- Manage - Explore: New button to delete queue is added and only visible for Expert Service (Admin)
Bug fixes
- Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They now better explain what you need them for and mention important security considerations.
- Create - Flow designer: Various small (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
- Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.
- Deploy - Releases: We fixed an issue, where after removing containers from a machine, during execution of the deployment plan, the removed containers are not recognized as change, causing the ‘Deploy machine’ step to be skipped.