Skip to Content

Changes for page 261 - Taking Charge

Last modified by Erik Bakker on 2026/02/12 09:08
From version 307.1
edited by Erik Bakker
on 2026/02/10 09:00
Change comment: There is no comment for this version
To version 270.1
edited by Erik Bakker
on 2025/07/14 07:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -261 - Taking Charge
1 +249 - Amendment Avalanche
Content
... ... @@ -1,16 +1,35 @@
1 -This release includes a lot of updates to our platform. We are releasing some beta features for customers utilizing our latest version of the API Gateway allowing to use multiple authentication methods. On top of that we will release a new environment template that will update a multitude of configurations on cloud and on-premise machines. Furthermore, we have a series of smaller improvements to bring delight to your everyday work.
1 +This release is characterized by many updates to our platform, both from a user perspective and from a technical perspective regarding our backend services. This sets us up to allow all users to prepare their Mendix systems for a migration to DSH (if applicable). Furthermore, it enables us to assist our users more effectively as they develop within the platform.
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.249 - Amendment Avalanche.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 authorization code will also obtain a ~~refresh token~~, that can be used to obtain a subsequent access token without user intervention. This refresh token is valid for *24 hours*, meaning that the client application has to call the eMagiz API gateway at least that often, otherwise manual intervention is needed to authorize the call again.
7 +* General - License Tracker: You can now see licensed flows on the model level alongside the company level after we have registered the correct configuration. (#859)
8 +* Event Streaming - DSH Connection: The eMagizConnector base image has been updated as preparation to support event streaming integrations on DSH. This allows all users to prepare their Mendix systems to connect to DSH.
9 +** Note that all users running the new eMagiz Connector will receive this update with their next release. **If you already have a running eMagiz Connector, you need to restart the application to retrieve the latest information after the new release is prepared for you. **
10 10  
11 -==== Remarks ====
11 +==== Minor changes ====
12 12  
13 -* The advised Docker version for on-premises deployments has been updated from 24.0.7 to 29.1.3. Documentation on how to update Docker can be found at:
14 -** [[Linux>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-linux-installguide.WebHome||target="blank"]]
15 -** [[Windows>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-windows-installguide.WebHome||target="blank"]]
16 -* An infrastructure change has been applied to the container registry to improve how traffic is managed within our own environment.
13 +* Event Streaming - User Management: When adding new event streaming integrations that link to an **existing** event streaming processor, you **must** transfer them to the Create phase via the adding integrations tooling in the Create. This will trigger eMagiz to update the Deploy user management accordingly.
14 +** This functionality applies to both the old and new event broker.
15 +* Design - Message Definition: The overview of the attributes shown in the entity overview of the data model (i.e., CDM) and the system message now also shows the description of the attribute. (#1671)
16 +* Create - Flow Designer: The circuit breaker option under the request handler advice chain can now also be filled with a property placeholder. (#1619)
17 +* Create - Flow Designer: The overwrite option of the headers of a standard header enricher is now placed in the 'Basic' tab instead of the 'Advanced' tab. (#1666)
18 +* Create - Flow Testing: When creating a new test message and selecting the option "from existing file", the default option is now "Create" instead of "Capture". (#1659)
19 +* Create - Flow Testing: Each trace entry in the "Traces" overview now contains a timestamp. (#1661)
20 +* Capture - Overview: Deleting systems/integrations/tenants in Capture now shows a progress bar. (#1665)
21 +* Deploy - Unused Properties: For the unused properties functionality on the Create Phase Release, it is adjusted so that only the properties that are not used in any of your releases across environments are shown. They can be deleted without impacting any of the existing releases. (#1244)
22 +** Context is added to guide users through the following actions.
23 +** Performance has improved significantly. As a result, the process takes less time than before.
24 +* Deploy - Releases: Promoting a release to the next environment does not trigger the auto-delete behaviour of releases anymore. (#1318)
25 +* Deploy - Containers: Only the active containers are updated when a user adds or removes something from a release. Consequently, when a new integration is added, inactive containers will not contain the new integration. They can be reactivated if desired to enable automatic updates again. (#986)
26 +
27 +==== Bug fixes ====
28 +
29 +* Create - Add Integrations: We fixed several issues regarding untransferring and transferring integrations. Among other things, we addressed the following specific cases.
30 +* Re-transferring integrations to Deploy
31 +* Untransfering the last integration of a system
32 +* Create - Flow Designer: The user can now completely read the alerts in the flow designer with a hover text. (#1168)
33 +* Create - Flow Designer: The "Allow empty array" checkbox in Create can now be used without it throwing an error. (#1640)
34 +* Create - Flow Designer: We ensured that the order in which you create flow versions for flows belonging to an "exit/entry" construction can be random. As a result, this will prevent users from ending up with only a part of the flows belonging to this construction in Deploy, while all flow versions are indeed created in Create.
35 +* Manage - Alerting - Triggers (Error): Error alerts with ‘not equal to’ and ‘does not contain’ evaluations on ‘exception class’ and/or ‘exception message’ will now only trigger if both the first and last exception don’t equal/contain the value. (#1576)