Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 13.1
edited by Erik Bakker
on 2022/10/24 13:35
Change comment: There is no comment for this version
To version 311.1
edited by Erik Bakker
on 2026/02/10 10:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -186 - Daemon Switch
1 +261 - Taking Charge
Content
... ... @@ -1,35 +1,43 @@
1 -The release brings the new monitoring stack to fruition and various updates to handling multiple namespaces. On top of that, we have released a sleuth of smaller feedback items and bug fixes.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.186 - Daemon Switch.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.261 - Taking Charge.WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 -* Generic - New monitoring stack: As of this release, you can run on the new monitoring stack. For more information on becoming an early adopter, don't hesitate to get in touch with us at productmanagement@emagiz.com
5 +==== New Features ====
7 7  
8 -=====Minor changes=====
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.
9 9  
10 -* Create - Flow designer: You can now see who/when a resource was changed on a resource view page.
11 -* Design - Solution: You will see a warning in the Solution view on operation if it is not connected to a backend API operation or in "Transformation" mode.
12 -* Create - Flow designer: You can see all related configurations that use a specific resource when viewing the details of the resource.
13 -* Design - API Gateway: Changes in your Gateway messages are reflected directly in your OpenAPI JSON document.
14 -* Model Dashboard - Going to manage from the model dashboard now loads the error message dashboard without having to click on the error messages dashboard explicitly
15 -* Create - Flow testing: The name of the starting point in the flow testing result tab is matched with the component type.
16 -* Deploy - Releases: The automated flow test pop-up can now be closed by pressing "Enter."
17 -* Deploy - Properties: Password-type properties are masked in the unused properties pop-up.
18 -* Deploy - User management: "Generate Keystore" button is renamed "Download Keystore," and the file name contains environment information.
19 -* Create - Flow Testing: Added a button to display the content of a selected trace message in a pop-out.
20 -* Deploy - Properties: You can use enter key to search on the property overview page.
21 -* Create - Flow designer: Increased size of the SpEL expression input field of standard transformer component.
22 -* Create - Flow Designer: Show generated resources toggle is not disabled by default; your preference for showing or hiding generated resources will be saved.
23 -* Administration - Licenses: Added event streaming storage usage of your models.
24 -* Store: Compatibility check is added, which prevents importing G3 store items into G2 flow/integration
25 -* General: Improved help texts explaining options and screens related to the new runtime architecture or the migration towards it.
11 +==== Major changes ====
26 26  
27 -====Bug fixes====
28 -* Deploy - Properties: Improved the layout of the cron trigger generator page
29 -* Deploy - Properties: Generating a password or CRON trigger will not reset the runtime field
30 -* Create - Flow designer: While editing an exit flow, the system message is not editable.
31 -* Design - Integration designer: For event streaming integrations, switching between Design Mapping and Create Transformation sometimes did not work.
32 -* Create - Transformation: For event streaming integrations, the 'Start editing' button sometimes did not work.
33 -* Create - Flow designer: Comparing two flow versions works again.
34 -* Create- Flow Designer: When creating my initial version of a flow, the notification pop-up shows the correct information.
35 -* Create - Flow Designer: All relevant support objects will be highlighted when selecting a support object.
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 +==== Minor changes ====
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)
29 +
30 +==== Bug fixes ====
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.
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.