Skip to Content

Wiki source code of 261 - Taking Charge

Last modified by Erik Bakker on 2026/02/10 11:42
Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}
3 (((
4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5
6 **Hi there, eMagiz developers!** 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.
7
8 == **New Environment Template** ==
9
10 As of this release, we have implemented various security and version updates regarding customer models. This is released as part of a new [[environment template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]. Note that this also will update your authorization server if applicable.
11
12 {{info}}The following applies to this functionality:
13 * This is only released for models running in **our current-generation architecture**. This includes the following:
14 ** Security improvements to the eMagiz infrastructure
15 ** Update Ubuntu version
16 ** Update Docker version
17 ** Update control agent version
18 ** Update Authorization Server (if applicable)
19 * The functionality will be made available as part of a new cloud template and can be updated via the default [[upgrade>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Cloud Management.novice-emagiz-cloud-management-cloud-templates-explained||target="blank"]] functionality.
20 * You need to update to this version of our cloud template before **March, 12th 2025**.{{/info}}
21
22 === **User name shown in HTTP Statistics**~* ===
23
24 The details page will now show the display name of the user that initiated a request instead of the Id.
25
26 {{info}}For this change to be applied to your environment, you need to adhere to the following requirements:
27 * The MAM API-Gateway migration must be completed
28 * You must be running on the latest environment template
29 ** Single lane: R18
30 ** Double lane: R20
31 ** The gateway container must be deployed with the latest eMagiz runtime (version 3.5.0 or up){{/info}}
32
33 === **Authorization Code Grant Type - Support**~* ===
34
35 * 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:
36 ** The authorization code is valid for **5 minutes**, meaning it should be used to obtain an access token within that period.
37 ** 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.
38
39 == **Minor Changes** ==
40
41 //__Security Headers__//
42 Improved security headers of the endpoints of eMagiz-hosted authorization servers.
43
44 //__Security Button__//
45 We have removed the security setting button from the API Gateway catalog. You can still access the settings from the design overview.
46
47 //__Show & Copy__//
48 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.
49
50 //__URL Information__//
51 Any reference to a URL related to the authorization server is now shown, including 'https://'.
52
53 //__Endpoint URL Information__//
54 Endpoint URL for routes are shown on the view/edit pop-up of specific routes on the Deploy architecture that run in your cloud. Additionally, the help text explains how the endpoint URL is constructed.
55
56 == **Bug Fixes** ==
57
58 //__Display Name__//
59 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.
60
61 //__Importing OpenAPI Specification - Design System Message__//
62 After successfully importing an OpenAPI file in the system request/response message, the user remains on the same page.
63
64 //__Failover Configuration__//
65 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.
66
67 //__Design Architecture - History__//
68 We inform the user via the History overview when an overwrite action is triggered in the test environment for their model upon request.
69
70 //__Create - Add Integrations__//
71 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.
72
73 //__Create - Flow Designer//
74 The help text of the XPath expression field on the XPath splitter is updated.
75
76 //__Create - Transformation__//
77 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.
78
79 //__Deploy - Start/Stop Flows__//
80 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).
81
82 === **Remarks** ===
83
84 * When retrieving information from our infrastructure about available customer agents, we improved performance by reducing the amount of data we retrieve and process.
85
86 == **Fancy Forum Answers** ==
87
88 As always, this is a gentle reminder to ask questions via the Q&A forum in the eMagiz iPaaS portal. This way, we can all benefit from the community's knowledge. For some inspiration, take a look at these forum answers:
89
90 * [[error converting a string to a double>>https://my.emagiz.com/p/question/172825635704298203||target="blank"]]
91
92 == **Key Takeaways** ==
93
94 Thanks to all who helped build the product and those who tested and provided feedback to improve it. To end this post, here are some key takeaways for you:
95
96 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
97 * If you have feedback or ideas for us, talk to the Platypus
98 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
99 * Clear your browser cache (Ctrl + Shift + Del)
100 * Check out the release notes [[here>>doc:Main.Release Information.Portal.261 - Taking Charge.WebHome||target="blank"]]
101 * Start thinking about how the license tracker can aid your development
102 * Start thinking about major, minor, and patch
103 * Keep making great integrations
104
105 Let's stay in touch and till next time!
106
107 {{info}}
108 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
109
110 {{/info}}
111 )))
112
113 (((
114 {{toc/}}
115 )))
116 {{/container}}
117 {{/container}}