Changes for page 266 - Feel Free

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-261 - Taking Charge
	1	+266 - Feel Free

Content

...	...	@@ -1,43 +1,31 @@
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 has a significant impact on users. Both in delivering functional value to our end users and in moving away from a legacy construct within our platform, and taking the UI one step into the future. On top of that, we have squashed some bugs. Sadly, however, we also have to announce that the announced **[[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** in [[release 264>>doc:Main.Release Information.Release Blogs.264 - Strict Separation.WebHome||target="blank"]] has been pulled due to not meeting quality standards. Having said that, enjoy reading our latest updates on 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>>doc:Main.Release Information.Release Blogs.266 - Feel Free.WebHome||target="blank"]].
4	4
5		-==== New Features ====
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.
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)
	7	+* General - Event Streaming: To authenticate at DSH, our event streaming broker, we use certificates. These certificates have an expiration date, so they must be rotated. We have introduced a new way of rotating these certificates for you.
	8	+** Proxy certificates must always be valid in DSH to prevent clients from encountering issues. A scheduled event runs daily during working hours to verify this.
	9	+** If certificate rotation fails in the test environment, it will **not** continue to the acceptance or production environments.
	10	+* General - Platform: Improved our general deletion behavior when deleting a model.
	11	+* Create - System: We now show the parent entity when selecting an entity or attribute in the right panel. This allows a user to identify better where in the message's structure they currently are. (#1520)
	12	+* Create - Add Integrations: Improved how we autogenerate flows for the user.
	13	+* Deploy - Release: Creating a new release automatically puts you in “edit mode” for that release. (#672)
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)
	17	+* Capture - Integration: Users are prevented from clicking the "Save integration" button too fast after creating a new message type to prevent a timing issue resulting in an error. The save button at the integration level is inactive until a message type is set for that integration. (#531)
	18	+* Design - Catalog: The default request body is generated automatically for the POST operation when added as an integration in the Design phase.
	19	+* Design - Edit an API integration - New/Edit resource: Added reserved keywords for the path of a resource, which can no longer be used. (#1585)
	20	+* Create - Transformation - Custom XSLT snippet: Trying to save a newly edited XSLT snippet is only possible in “Edit mode”. (#1670)
	21	+* Deploy - Architecture: Fixed an issue in the execution of the environment upgrade for models that have API MAM.
	22	+* Deploy - Upgrade: Fixes a bug where the portainer agent could not be updated, as part of the environment template procedures, for Windows systems where portainer is installed on another drive than C:\. [CSP-1922]
	23	+* Deploy - History: Entries stating 'null' will no longer be shown. (#1479)
	24	+* Manage - Monitoring - HTTP Statistics (Other metrics): The mean and max for the response time are split into two graphs. (#1200)
	25	+* Manage - Monitoring - Log Entries: The search/reset buttons are disabled while the reset/search is still being processed. (#1538)
40	40
41	41	==== Remarks ====
42	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.
	29	+* General - Infrastructure: An update has been applied to the internal communication with the eMagiz-managed authorization server.
	30	+* General - Platform: An update has been applied across the platform regarding the UI. As a result, all reference selectors have been replaced with combo boxes, aligning with current best practices and enabling users to interact with the platform more effectively.
	31	+** Slightly modified the creation of new message types by implementing a new type of input widget that combines drop-down selection functionality with actions.