Skip to Content

Changes for page 217 - Template Tango

Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 6.1
edited by Erik Bakker
on 2022/10/14 13:53
Change comment: There is no comment for this version
To version 69.1
edited by eMagiz
on 2023/04/25 13:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - Get Ready
1 +196 - Last Post
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.eMagiz
Content
... ... @@ -1,24 +1,39 @@
1 -Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities.
1 +Here's our first release of this quarter. Key focus remains on Flow testing, additional results of the Hackathon and API Gateway improvements
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.185 - Get ready.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.196 - The Last Post.WebHome||target= "blank"]].
4 4  
5 5  =====New features=====
6 -* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file.
7 7  
7 +* 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.
8 +* Deploy - Architecture: You can now find the Static IP address of connector machines when you update to the new cloud template.
9 +
8 8  =====Minor changes=====
9 9  
10 -* Design System. Changed the look and feel across the portal altogether. Changes can be seen in:
11 - ** Datagids, where there is now on hover action for example.
12 - ** Pop ups
13 - ** Context menus, also have on hover action
14 - ** Styling of scrollbars
15 -* Message Redelivery - admin logs improved to better analyze issues when they occur
16 -* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality
17 -* Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed
12 +* Deploy - Architecture: The topics are now ordered alphabetically and the runtimes will now get the same order as design architecture (after ‘apply to environment’)
13 +* 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.
14 +* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran.
15 +* Administration-User management: Company contact can edit permissions of models that fall under child companies
16 +* Administration: Contracts page removed
17 +* Create-Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter.
18 +* 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.
19 +* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
20 +* 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.
21 +* 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.
22 +* 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.
23 +* 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.
24 +* 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.
25 +* 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.
26 +* 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.
27 +* 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
28 +* Create - Flow designer: Improve responsiveness of resources tab at right panel
29 +* Manage - Explore: New button to delete queue is added and only visible for Expert Service (Admin)
18 18  
19 19  ====Bug fixes====
20 -* Deploy - Deployment plan. Performance of page to deploy a release increased significantly
21 -* Store - Import resources was incorrectly done in specific cases, which is now fixed
22 -* Store - Target namespace will be imported when imported XML Message Definition
23 -* Store - When exporting components, if property values contains bus name, they will be updated automatically with new bus name when importing into a new bus.
24 -* Store: Importing items from the store sometimes resulted in invalid JMS connection factories.
32 +
33 +* 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.
34 +* 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.
35 +* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.
36 +* 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.
37 +
38 +====Remarks====
39 +