Skip to Content

Changes for page 248 - Smooth Sailing

Last modified by Erik Bakker on 2025/06/30 13:33
From version 71.1
edited by Erik Bakker
on 2023/04/25 16:36
Change comment: There is no comment for this version
To version 270.1
edited by Erik Bakker
on 2025/06/30 09:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -196 - Last Post
1 +248 - Smooth Sailing
Content
... ... @@ -1,38 +1,21 @@
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.
1 +This release introduces a new [[cloud template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]], for every type of cloud we offer that connects you to our latest carwash. In addition, we have several improvements within the platform that enhance the user experience and improve interaction with the platform. See below for the details.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.196 - The Last Post.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.248 - Smooth Sailing.WebHome||target="blank"]].
4 4  
5 -=====New features=====
5 +==== Major changes ====
6 6  
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.
7 +* General - Cloud Template: A new [[cloud template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]], for every type of cloud we offer, is available that enables connections to be switched to the updated carwash.
8 +* Create - Transformation: Users are allowed to move operations freely, except for Static Input, which must always be the first operation.
9 +** Deleting the Static Input operation is not allowed if there are other operations in the row.
10 +** An error message is presented in the alert tab if there is a mismatch between the input and output of an operation to show that the order is inconsistent. The alerts can be pressed to open the edit or view screen of the operation that is causing the inconsistency.
8 8  
9 -=====Minor changes=====
12 +==== Minor changes ====
10 10  
11 -* Deploy - Architecture: The topics are now ordered alphabetically and the runtimes will now get the same order as design architecture (after ‘apply to environment’)
12 -* 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.
13 -* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran.
14 -* Administration-User management: Company contact can edit permissions of models that fall under child companies
15 -* Administration: Contracts page removed
16 -* Create-Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter.
17 -* 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.
18 -* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
19 -* 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.
20 -* 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.
21 -* 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.
22 -* 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.
23 -* 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.
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 -* 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.
26 -* 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
27 -* Create - Flow designer: Improve responsiveness of resources tab at right panel
28 -* Manage - Explore: New button to delete queue is added and only visible for Expert Service (Admin)
29 -
30 -====Bug fixes====
31 -
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 -* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.
35 -* 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.
36 -
37 -====Remarks====
38 -
14 +* Permissions - History: The export of a model ‘permissions’ tab now has a logical name. (#857)
15 +* Design - Message Mapping: Users can now refresh their Design message mappings. (#848)
16 +* Deploy - Architecture: Previously canceled containers, machines, and connectors in Design → Architecture are no longer shown in the 'Apply to Environment' overview in Deploy. (#1646)
17 +* Deploy - Releases: Users can now add every type of flow to their release. (#948)
18 +* Deploy - Containers: The successful deletion pop-up is prevented from showing when the process is unsuccessful. This action occurred when a user tries to delete an empty container with hidden flows attached. (#1481)
19 +* Deploy - User Management: For the new screens related to DSH user management, we have fixed some undesired behavior caused by Keeper Password Manager.
20 +** Prevent auto-fill on specific fields by renaming labels
21 +** Applied styling to hide the Keeper button in input fields where undesired.