Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 136.1
edited by CarlijnKokkeler
on 2023/10/23 16:40
Change comment: There is no comment for this version
To version 312.1
edited by Erik Bakker
on 2026/02/10 11:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +261 - Taking Charge
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,46 +1,43 @@
1 -In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
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.207 - Aligned State .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 -* State generation: New state generation features have been added. Please check out [[V2.0.0>>Main.Release Information.Runtime Images.V2.0.0||target="blank"]] [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.
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 -* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
11 -* Create - Framework: The framework used in the flow designer has been updated, improving performance.
12 -* Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing.
13 -* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009)
14 -* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
15 -* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
16 -* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
17 -* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
18 -* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
19 -* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
20 -* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
21 -* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
22 -* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069)
23 -* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
24 -* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
25 -* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action.
26 -* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.
11 +==== Major changes ====
27 27  
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.
28 28  
16 +==== Minor changes ====
29 29  
30 -====Bug fixes====
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)
31 31  
32 -* Design - Store: We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
33 -* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
34 -* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
35 -* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888)
36 -* Design - Store: Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message. (#1027)
37 -* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.
38 -* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
39 -* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
40 -* Manage - Monitoring: It is now possible to search on messages using partial search words in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
30 +==== Bug fixes ====
41 41  
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)
42 42  
41 +==== Remarks ====
43 43  
44 -=====Infra and image changes=====
45 -
46 -* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.
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.