Skip to Content

Changes for page 217 - Template Tango

Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 42.1
edited by Erik Bakker
on 2023/01/18 11:32
Change comment: There is no comment for this version
To version 73.1
edited by Erik Bakker
on 2023/04/28 08:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +196 - The Last Post
Content
... ... @@ -1,32 +1,35 @@
1 -The release finishes up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs and some minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
1 +Here's our first release of this quarter. We have delivered additional small (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 improvements in the way of work for nextGen environments.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.190 - Fast Forward.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 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
7 -* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your jms-server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime.
8 8  
9 -=====Major changes=====
7 +* Create - Flow Testing: Till now, the Flow Testing allowed to test eMagiz flows by defining a testing point on the start (and end) point(s), run them and compare the actual and expected messages. In this release, “Live Mode Testing” is introduced, making it possible to test communication with an actual "live" endpoint. As a result a “HTTP outbound gateway” can be set in “Live Mode”. When you do this, the HTTP outbound gateway will send its HTTP request to the actual 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.
10 10  
11 -* Manage - Redelivery: You are able to explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Beside that, you are also able to redeliver the message(s) in this page.
12 -
13 13  =====Minor changes=====
14 14  
15 -* Design - System message: 'Request' and 'Response' entities are generated and set as root entities automatically for new SOAP web service integrations in 3rd generation runtimes.
16 -* Create - Flow designer: sensitive information stored in property values is masked. (#790)
17 -* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so user can use it to compare with the previous versions.
18 -* Create - Flow Designer: when importing store item from another partner, a error popup will be shown instead of default error message.
19 -* Deploy - Releases: The activate release functionality gained a performance improvement for gen 3 models.
20 -* Deploy - Architecture: Before apply to environment, we require a confirmation from you if those are some breaking changes that may cause issues in AWS. (#828)
21 -* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
22 -* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings", where you can enable/disable both HTTP and control bus per runtime.
23 -* Deploy - Releases - When activating a release you will be reminded of empty runtimes. Empty runtimes are runtimes without flows in the release. These runtimes should be removed from your architecture.
11 +* 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.
12 +* 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.
13 +* 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.
14 +* 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.
15 +* 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.
16 +* Create - Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter.
17 +* Create - Flow designer: Improve responsiveness of resources tab at right panel.
18 +* Create - 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.
19 +* 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.
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 in order to obtain its name
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’)
25 +* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran.
26 +* Manage - Explore: A new button to delete queue is added. This button is only visible for authorized personnel.
27 +* Administration -User management: Company contact can edit permissions of models that fall under child companies.
28 +* Administration - Overview: Contracts page removed.
24 24  
25 25  ====Bug fixes====
26 -* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
27 -* Create - Flow Designer: When copy and paste, support objects such as "property placeholder", "support.bus-connection-caching" and "support.bus-connection-plain" are not duplicated (#793)
28 -* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in setup step.
29 -* Deploy - Containers: We fix an issue that the container overview does not show the entry flows which should run on that container. (#863)
30 -* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
31 -* Deploy - Architecture: The deploy runtimes option is only visible for admin. New menu item "Deploy agent" is added and visible for all users to show the command which can be uses to deploy agent on premises machine.
32 32  
32 +* 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.
33 +* 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.
34 +* 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.
35 +* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.