Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 59.1
edited by Erik Bakker
on 2023/03/14 08:51
Change comment: There is no comment for this version
To version 74.1
edited by Erik Bakker
on 2023/04/28 08:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -194 - Giant Leap
1 +196 - The Last Post
Content
... ... @@ -1,33 +1,39 @@
1 -The release introduces various improvements on our 3rd generation runtime architecture and various other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements.
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.194 - Giant Leap.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 6  
7 -* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V131.WebHome||target="blank"]].
8 -* Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers and waking up a cloud slot will start those containers. (#889)
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.
9 9  
9 +=====Major changes=====
10 +
11 +* 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.
12 +
10 10  =====Minor changes=====
11 11  
12 -* Create - 3rd generation runtime migration: When migrating your event streaming container to the 3rd generation runtime, the event streaming infra flow will be updated correctly based on whether you are using custom error handling on your event processors or not.
13 -* Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807)
14 -* Deploy - User Management: Roles are sorted alphabetically. (#806)
15 -* Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup. Please use the ‘Upgrade’ feature to keep your cloud architecture up-to-date.
16 -* Manage - Event Streaming Statistics: Updated graphs to display the average of the selected timeframe, added help texts to each table and graph and made some small visual improvements.
17 -* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833)
15 +* 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.
16 +* Design - Store: We updated importing to help you avoid an error while importing store items that will break your message definition in some cases.
17 +* 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.
18 +* 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.
19 +* 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)
20 +* Create - Flow designer: Model resources tab removed on the resources page when adding a resource to a validating filter. (#921)
21 +* Create - Flow designer: Improve the responsiveness of the resources tab on the right panel.
22 +* 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.
23 +* 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.
24 +* 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.
25 +* Create - Resources: When viewing a resource, its full name will be shown, removing the need to download the resource to obtain its name. (#922)
26 +* 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.
27 +* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
28 +* 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)
29 +* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are run.
30 +* Manage - Explore: A new queue delete button is added. This button is only visible to authorized personnel.
31 +* Administration -User management: Company contact can edit permissions of models that fall under child companies. (#895)
32 +* Administration - Overview: Contracts page removed. (#907)
18 18  
19 19  ====Bug fixes====
20 20  
21 -* Generic: We fixed an issue that you may see a screen with a broken styling when switching among phases.
22 -* Create - Flow Designer: Removed the option to create a new resource on resource selection pop-up of simple XSD schema support object.
23 -* Create - Flow designer: We fixed the flow generation of entry flows for API Key secured API Gateway operations. This problem was introduced in version 193 (2023-02-04). (#902)
24 -* Create - Resources: We fixed an issue when deploying flows with uploaded resources with very long filename (>100 characters).
25 -* Deploy - Releases: You need edit rights in test environment of deploy phase to execute “Update flows to latest versions” action.
26 -* Manage - Dashboard: We update the view to visualize the split entries after you do a migration a combined entries.
27 -* Manage - Logging: When a container cannot be started due to an incorrect stylesheet, the error message will include what the error is and in which stylesheet is occurred (#825)
28 -* Manage - Logging: Reduced the occurance of 'Failed to send to Elastic' log messages which triggers alerts. (#898)
29 -* Manage - Alerting: Editable column shows the correct value.
30 -
31 -====Remarks====
32 -
33 -* Create - Flow designer: After the deployment, the ‘Version Compare' and 'Version Restore’ features will be unavailable for a few hours, because of data migration. You will get an error stating that the version is not compatible with the selected feature until migration has finished.
36 +* 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.
37 +* 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.
38 +* 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)
39 +* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.