Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 88.1
edited by Erik Bakker
on 2023/06/06 08:36
Change comment: There is no comment for this version
To version 76.2
edited by Erik Bakker
on 2023/05/09 13:47
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -199 - Home Improvements
1 +197 - Pay Attention
Content
... ... @@ -1,20 +1,35 @@
1 -In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture, the store, security, and certificate management.
1 +Here is our first release of this quarter. We have delivered additional minor (bug) fixes in this release and released the Live Flow testing feature. The last is a real improvement during the development process of a flow. Furthermore, you will find several enhancements in working in nextGen environments.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.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 +=====New features=====
6 +
7 +* Create - Flow Testing: Till now, Flow Testing allowed to test eMagiz flows by defining a testing point on the start (and end) point(s), running them, and comparing the actual and expected messages. In this release, "Live Mode Testing" is introduced, making testing communication with an actual "live" endpoint possible. As a result, an "HTTP outbound gateway" can be set in "Live Mode." When you do this, the HTTP outbound gateway will send its request to the endpoint. Consequently, the response will be handled by the flow in the flow test so you can determine whether the actual endpoint behaves as expected.
8 +
5 5  =====Minor changes=====
6 6  
7 -* Design - Message mapping: It is now possbile to create a message mapping to an imported system message from the store.
8 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 -* Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud. This way, you no longer have to contact your partner manager to retrieve this information. To use this functionality, please ensure you upgrade (automatically) to the latest cloud template. (#899)
10 -* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately three months before event streaming users' access certificates expire.
11 -* Deploy - Release: Unused runtime images will be automatically removed after successful machine deployments. This can be disabled by changing the machine step in your deployment plan.
12 -* Manage - Monitoring: HTTP statistics page now displays all the resources. (#960)
13 -* Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it.
14 -* General - Infra: Changed the library for storing metadata in the eMagiz Control Tower.
11 +* Design - Store: You can encounter a warning message when you import a transformation from the store because your imported transformation requires information from the related store fragment. To avoid a non-functional transformation in the Create phase, you should include that store fragment. Afterward, we will update your default flow component transformer to make it work correctly.
12 +* Design - Store: We updated importing to help you avoid an error while importing store items that will break your message definition in some cases.
13 +* Design - Store: We fixed an issue that you import the message definition(s), and a specialized DataType of imported message definition(s) is not matched with the exported message definition(s). Now, they are matched, and your transformation won't get issues.
14 +* Create - Store: We automatically excluded resources that are not good enough from the exporting wizard. Then you will find it easy to recognize a problem and avoid creating unusable store items.
15 +* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can only change the CDM message definition, Gateway message definition, or even Event streaming message definition with the proper rights. (#690)
16 +* Create - Flow designer: Model resources tab removed on the resources page when adding a resource to a validating filter. (#921)
17 +* Create - Flow designer: Improve the responsiveness of the resources tab on the right panel.
18 +* Create - Flow Designer: Resources in the "Unused resources" section can be marked as used when components refer to the resources through property placeholders or in custom SPeL expressions.
19 +* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests if that parameter was not supplied, so please reset your entry flow to apply the fix.
20 +* 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.
21 +* Create - Resources: When viewing a resource, its full name will be shown, removing the need to download the resource to obtain its name. (#922)
22 +* 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.
23 +* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
24 +* Deploy - Architecture: The topics are now ordered alphabetically, and the runtimes will now get the same order as design architecture (after 'apply to environment') (#543)
25 +* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are run.
26 +* Manage - Explore: A new queue delete button is added. This button is only visible to authorized personnel.
27 +* Administration -User management: Company contact can edit permissions of models that fall under child companies. (#895)
28 +* Administration - Overview: Contracts page removed. (#907)
15 15  
16 16  ====Bug fixes====
17 17  
18 -* Create - Store: Spring Reserved words containing * are not incorrectly replaced with the flow prefix. (#864)
19 -* Manage - Monitoring: Not all log messages were visible in the manage phase when an application failed to start. Note that this functionality requires a newly deployed release. (#937)
20 -
32 +* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They better explain what you need them for and mention essential security considerations.
33 +* Create - Flow designer: Various minor (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
34 +* Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514)
35 +* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs. (#940)