Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06

From version 317.1
edited by Erik Bakker
on 2026/02/20 13:26
Change comment: There is no comment for this version
To version 71.1
edited by Erik Bakker
on 2023/04/25 16:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -262 - Good News
1 +196 - Last Post
Content
... ... @@ -1,28 +1,38 @@
1 -This release includes many updates to our platform. We are releasing some beta features for customers using our latest version of the API Gateway, allowing them to use multiple authentication methods. On top of that, we have also launched a new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers. Furthermore, we have a series of smaller improvements to enhance your everyday work.
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>>doc:Main.Release Information.Release Blogs.262 - Good News.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 -==== Minor changes ====
5 +=====New features=====
6 6  
7 -* General - Runtime Image: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers is available.
8 -* Create - Flow Designer: The help text for the Result Type attribute of the JSON to XML transformer has been improved. (#1553)
9 -* Deploy - Releases: The on‑hover text for a release also displays the most recent date and time the release was edited. (#341)
10 -* Create - Flow Designer: Unused support objects can be deleted with a single button. (#794)
11 -* Deploy - User Management: For models that have been migrated to our latest functionality for both our event streaming and API offering, changes to users in the Deploy phase will be applied immediately for both manually created users and system users.
12 -* Deploy - Architecture: The Apply to Environment pop-up has been updated to reflect progressive changes made to specific objects. Any pending changes on Container, Router, Certificate, Instance, and AWS resources are now stacked and displayed to the user. The list is ordered from the earliest change at the top to the most recent at the bottom, allowing users to clearly see all modifications made to a specific object until the Apply to Environment button is clicked. These changes will remain active for future operations. (#1537)
13 -* Deploy - Architecture - Routes: The View and Edit pages for Routers have been updated to remove the Endpoint DNS Name and Flow Symbolic Name fields. (#1537)
14 -* Manage - Alerting: For Log and Error triggers, a custom subject can now be specified under ‘notifications’. This enables you to sort incoming alerts in your mailbox more easily.
15 -* Manage - Alerting: We have tightened the allowed characters for the triggers to reduce further the likelihood of HTML injection into the bodies of alerting emails sent by eMagiz.
16 -** Note: if you already have existing alert rules that contain characters that are now considered illegal, you will need to change them when you make any change to that trigger.
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.
17 17  
18 -==== Bug fixes ====
9 +=====Minor changes=====
19 19  
20 -* Create - FlowDesigner: When using DSH support objects, the required admin-only fields are automatically filled in. (#1755)
21 -* Create - Untransfer integration: We fixed an issue where you could not remove an integration of the Mendix connector system, which was migrated from the Legacy eMagiz Mendix Connector to the current eMagiz Mendix Connector in Create.
22 -* Design - Catalog: Help texts related to “content”, “Json format”, and “Gateway message definition” are updated. (#1082)
23 -* Create - Store: When importing a store component with properties, validation feedback will now be provided if the property value does not align with the expected type. (#1276)
24 -* Manage - Explore: Error message is much more descriptive when the container is not running (#1321)
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)
25 25  
26 -==== Remarks ====
30 +====Bug fixes====
27 27  
28 -* General - Infrastructure: We updated our image builder for Windows images to use the latest Java versions for images. Effectively, this means that any image built for Windows from this release onwards that uses a base image //3.4.0// or above, will use Java 21.0.10 as baseline. Images below version //3.4.0// will now use Java 17.0.18. Therefore, new (property) releases that use the same eMagiz base image, will still use a different Java version, and may therefore have some changed behavior. Normally that would not be noticable, but since these Java version increases drops support for some weak cipher suites, connectivity may be affected. For more information, please refer to the release notes of image 3.5.1.
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 +