Skip to Content

Changes for page 261 - Taking Charge

Last modified by Erik Bakker on 2026/02/12 09:08
From version 313.1
edited by Erik Bakker
on 2026/02/12 09:08
Change comment: There is no comment for this version
To version 273.1
edited by Erik Bakker
on 2025/07/28 12:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -261 - Taking Charge
1 +250 - Fix Fest
Content
... ... @@ -1,43 +1,49 @@
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 will release new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** that update a multitude of configurations on cloud and on-premises machines. Furthermore, we have a series of smaller improvements to enhance your everyday work.
1 +This release features numerous updates to our platform, with a user-centric focus. This release, we once again embarked on our traditional Hackathon journey, focused on making the lives of our day-to-day platform users easier.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.261 - Taking Charge.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.250 - Fix Fest.WebHome||target="blank"]].
4 4  
5 -==== New Features ====
5 +==== New features ====
6 6  
7 -* API gateways using the latest Multiple Authentication Methods feature can now configure the [[Authorization Code OAuth2 grant type>>https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow||target="blank"]] for their gateway users. Note that the following timeouts apply:
8 -** The authorization code is valid for **5 minutes**, meaning it should be used to obtain an access token within that period.
9 -** Clients that obtain an access token with an authorization code will also obtain a //refresh token//, which can be used to obtain a subsequent access token without user intervention. This refresh token is valid for **24 hours**, meaning the client application must call the eMagiz API gateway at least that often; otherwise, manual intervention is needed to authorize the call again.
7 +* Create - Flow Designer: Custom resources in the form of XSLT files and Groovy scripts can be previewed and edited directly in the flow designer. (#1115)
8 +* Create - Flow Designer: Two navigation buttons (Start/Stop editing and “Open in Design“) are added to the following pages. (#1607)
9 +** Messaging:
10 +*** System message
11 +*** CDM message
12 +** API gateway:
13 +*** Gateway message
14 +*** System message
15 +** Event streaming:
16 +*** Topic in
17 +*** Topic out
10 10  
11 -==== Major changes ====
12 -
13 -* Deploy -> Architecture (Upgrade): The authorization server has been incorporated into the environment template. The first deployment will happen in Deploy > Architecture. All infra-side updates will be covered within the environment upgrade.
14 -* Deploy -> Architecture (Upgrade): Double lane models can now upgrade to an intermediate environment template first, before upgrading to the final template in case of a service-impacting template. This allows us to verify that all containers in the backup zone are running properly before the final, service-affecting template is applied.
15 -
16 16  ==== Minor changes ====
17 17  
18 -* Generic -> Authorization Server: Improved security headers of the endpoints of eMagiz-hosted authorization servers.
19 -* Design -> Security: Removed the security setting button from the API Gateway catalog. You can still access the settings from the design overview.
20 -* Deploy: All pop-ups showing important information, like a key, secret, or password, are structured so that the data is visualised and can be copied by the user when the “show data” action button is utilised. (#1735)
21 -* Deploy -> User Management: Any reference to a URL related to the authorization server is now shown, including ‘https://'.
22 -* Deploy -> Architecture: Endpoint URL for routes is available on the view/edit pop-up of specific routes on the Deploy architecture. Additionally, the construction of how it is provided as a help text, and this feature is only available for the AWS model. (#792)
23 -* Manage -> Monitoring (HTTP Statistics): The details page will now show the display name of the user that initiated a request instead of the Id. Note: For this change to be applied to your environment, you need to adhere to the following requirements:
24 -** The MAM API-Gateway migration must be completed
25 -** You must be running on the latest environment template
26 -*** Single lane: R18
27 -*** Double lane: R20
28 -*** The gateway container must be deployed with the latest eMagiz runtime (version 3.5.0 or up)
21 +* General - Export: When exporting to PNG, the filename now has a logical name, containing the technical name of your model, the phase that was exported, and the time of the export. (#266)
22 +* Capture - Settings: This overview will now show the technical names, when known, of systems as well as their display name. (#810)
23 +* Capture - System: Users can quickly create multiple tenants in a multi-tenant system by using the new button called “Save and add new”. The button saves the previously created tenant and opens a new page to create a new tenant. (#1527)
24 +* Design - Settings: Make clear that only the model owner can alter the settings displayed under Design - Settings (#1638)
25 +* Create - Flow Designer: The expressions of recipient routers are visible in the grid to show the conditions along with them. Additionally, the grid has been updated to Data Grid 2, which offers a more visually appealing display. (#1649)
26 +* Create - Transformation: When viewing a transformation with a datatype conversion from or to ‘date’, ‘time’, or ‘datetime’, the time zone used in the formatting is now shown without the need to enter edit mode. (#945)
27 +* Deploy - Releases: We have updated the UI and user experience in Release > Details > Flow versions and Integrations tabs. Furthermore, we have added the option to display the integration name rather than the message type name, allowing you to see which API operation you are adding or removing from a release. (#1581)
28 +* Deploy - Architecture: Cloudslots that do not have an active environment will not be planned to be upgraded anymore, removing unnecessary emails being delivered to model owners. (#1594)
29 +* Deploy - Properties: Updated hover text of the generate button to reflect that values will be replaced. (#1160)
30 +* Manage - Error Messages: Users with view rights in Manage can now change the status of error messages. (#1669)
29 29  
30 30  ==== Bug fixes ====
31 31  
32 -* Generic: System display names in all phases are updated progressively with the change in the Capture phase. All other places where the system display name was allowed to be changed are now disallowed, and changes can only be made from Capture. (#449)
33 -* Design - System Message: After successfully importing an OpenAPI file in the system request/response message, the user remains on the same page. (#1308)
34 -* Design - System (Failover): When you identify a system as a failover and subsequently create the integration on that system, you do not need to push multiple versions anymore before you can deploy your release.
35 -* Design - Architecture: We inform the user via the History overview when an overwrite action is triggered in the test environment for their model upon request. (#1697)
36 -* Create - Flow Designer: The help text of the XPath expression field on the XPath splitter is updated. (#1467)
37 -* Create - Transformation: Users can mark all XPath expressions as checked by a button in the transformation page. This button will remove only the warnings that come with the import from store feature, and will delete only those with an XPath expression.
38 -* Create - Add Integrations: When creating a new event processor with JSON as input and XML as output, this configuration is reflected in the generated flow in Create after transfer. Now the message format is automatically recognized and handled correctly, similar to API Gateway operations. (#1752)
39 -* Deploy - Architecture (Start/Stop Flows): Your search phrase when searching for “component names” in this overview can now contain special characters present in the technical name of your inbound component(s). (#1639)
40 -
41 -==== Remarks ====
42 -
43 -* Generic: When retrieving information from our infrastructure about available customer agents, we improved performance by reducing the amount of data we retrieve and process.
34 +* Design - Message Tree: Attribute order is exchanged between the moved attributes rather than making an algebraic calculation to obtain a new value to avoid double jumps during the movement. (#1593)
35 +* Create - Message Definition: A longer time is given to the user to change the fields. Additionally, the pattern field is no longer time-bound, as it requires a longer input. (#1575)
36 +* Create - Flow Designer: Validation in JDBC stored procedure inbound channel adapter is now shown on the right element. (#1557)
37 +* Create - Flow Designer: Wiretap channel does not cause an error when its ID is too long. (#1606)
38 +* Create - Flow Designer: When changing a filter with a discard channel to start throwing exceptions on rejection instead of sending them to the discard channel, the UI will now correctly reflect this. (#1621)
39 +* Create - Flow Designer: When copying a component which have a field value longer than 64 characters and contains the flow’s name, then pasting, the field will not be limited to 64 characters. (#1398)
40 +* Create - Flow Designer: Linetokenizer -> Strict of the Flat file to XML transformer and 'Allow empty array' of the system message are not editable anymore when not in 'start editing'. (#1612)
41 +* Create - Transformation: Users are now able to switch between “Custom XPath” and “Convert datatype” options for the “Transform from date/time” transformer. (#1662)
42 +* Create - Transformation: Users can return to the correct design phase message mapping. (#1348)
43 +* Create - Transformation: User permissions are modified for the From Boolean Transformer so that the user can see the Value Mappings. (#1622)
44 +* Create - Flow Testing: Flow tests that contain Kafka Message Listener Adapter components can be executed again. (#1672)
45 +* Create - Create Flow Version: We fixed an issue where you got an error, which requires Deploy permission, when you create and transfer the new API operation to Deploy, since you only have permission in Capture, Design, and Create. (#1677)
46 +* Deploy - Architecture: You were able to remove pending changes from Deploy Architecture without applying them when pressing cancel after applying changes for a double lane model. (#1651)
47 +* Deploy - Architecture: Resolved the issue where enabling/disabling SSL-configuration in runtime settings could lead to duplicated help text. (#1455)
48 +* Deploy - User Management: We fixed an issue where the list of API operations did not show since these API operations were assigned to the related user. (#1678)
49 +** Additionally, help text is converted to the latest help text format.