Changes for page 275 - Summer Sounds

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-261 - Taking Charge
	1	+275 - Summer Sounds

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 includes several smaller improvements across the platform's phases. We also updated certain parts of our Mendix project to their latest versions.
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.275 - Summer Sounds.WebHome||target="blank"]].
4	4
5		-==== New Features ====
	5	+==== Minor Changes ====
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 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.
	7	+* General - Platform: As part of our regular system maintenance, we have upgraded the application to the Mendix LTS version 11.12.
	8	+** This upgrade improves the platform's overall stability, security, and long-term reliability. This upgrade has no impact on daily operations.
	9	+** This update ensures the application remains well-supported and ready for future enhancements.
	10	+* General - eMagiz Connector: We will release a new version of the eMagiz Connector (1.2.0) that is compatible with Mendix 11 (11.12.1 and higher).
	11	+* General - Legacy Event Streaming Broker: Updated Kafka Broker version from 3.8.1 to 3.9.2. This is a maintenance update and should not affect any functionality.
	12	+* Create - Flow designer: Various updates to flow designer components are introduced in preparation for the Spring 7 migration.
	13	+** Two support object components are no longer available to create in the current generation.
	14	+*** Access decision manager
	15	+*** OAuth2 Bearer token authentication filter.
	16	+** We updated validation for a few components in preparation for the Spring 7 migration to address missing or incorrect settings after the components are saved. Note that these updated settings can lead to alerts when opening a flow that currently has an incorrect configuration
	17	+*** File inbound channel adapter
	18	+*** TCP inbound channel adapter
	19	+*** JMS outbound gateway
	20	+*** Standard content enricher > Property
	21	+*** HTTP security
	22	+** On top of that, some components are end of support. They are no longer used in any client model and are therefore removed from the list of selectable Flow Designer components.
10	10
11		-==== Major changes ====
	24	+===== Bug Fixes ====
12	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.
	26	+* Design - Architecture: Updated display order calculation for machines when adding or moving them. (#1113)
	27	+* Deploy - Swagger UI: Downloaded Swagger documentation has the full correct schema. (#1811)
15	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	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.
	31	+* Updated various UI related modules within our Mendix project to their respective latest version.