Changes for page 262 - Good News

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-241 - Wild West
	1	+261 - Taking Charge

Content

...	...	@@ -1,41 +1,43 @@
1		-In the last sprint, we have released a lot in terms of usability improvements while working within the various phases of eMagiz and when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]] containing a much-needed improvement regarding deployment executions when working with state generation and code mappings on top of various improvements in our underlying code.
	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.241 - Wild West.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====
	5	+==== New Features ====
6	6
7		-* Deploy - Releases: A comparison feature for the Deploy phase is added. The comparison feature allows users to compare releases to track the differences in property values of those releases. The feature also provides information on who made the changes. The differences are categorized by “InRelease” and “NotInRelease,” which means that the additional property value is either in the first selected release (InRelease) or the second selected release (NotInRelease).
8		-** This functionality only works for releases created **after** this release.
	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		-====Minor Changes====
	11	+==== Major changes ====
11	11
12		-* Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471)
13		-* Capture - Add Integration: Removed the ‘remarks’ field from the ‘New Integration’ screen in Capture because this field was not visible enough in the rest of the portal. (#1608)
14		-* Capture / Design: For new systems, message types, machines, tenants, and models, hyphens are **no longer allowed** in the technical name. The technical name can only consist of lowercase letters and digits and must start with a letter. This also applies to systems, message types, and tenants that have not yet been transferred from design to creation. The portal will give an error message while transferring, and the hyphen has to be removed manually.
15		-* Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554)
16		-* Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616)
17		-* Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure.
18		-* Infra - Security: Improved security by implementing additional safeguards for AWS native services.
	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.
19	19
20		-====Bug fixes====
	16	+==== Minor changes ====
21	21
22		-* Capture - Add System: A loading bar is displayed before showing the pop-up when a user tries to create or edit a system. (#1228)
23		-* Capture - Edit System: When editing a system, the validation now considers that the name cannot be an empty string. (#1562)
24		-* Design - Message Definition: Two minor improvements are introduced:
25		-** The widget prevents users from adding the same message attribute within a message definition multiple times.
26		-** When adding a new message entity within your message definition and expanding the existing message definition, it doesn’t throw an exception when the user presses the Save button multiple times in a short time frame.
27		-* Design - Catalog: When creating the Swagger JSON, all custom examples users add will be shown correctly when displaying the Swagger. (#1597)
28		-* Design - Solution Architecture: When modifying the number of runtimes of a system, the validation will now take into account that the value may not be empty (#1513)
29		-* Create - Add Integrations: Users can untransfer a flow even when there is a property attached to the flow. (#1590)
30		-* Create - Add Integrations: When an integration is transferred from the Create phase, the flow, flow versions, and the corresponding integration in the Deploy phase are cleaned.
31		-* Create - Components: The browser page now displays the correct page title (#1509)
32		-* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549)
33		-* Create - Flow Designer: The default name of the REST template support object generated in passthrough API gateway operations now matches the (technical) name of the integration. (#1560)
34		-* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already an existing property description. (#1526)
35		-* Deploy - Environment Template: Fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly.
36		-* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore moves the user to the queue browser of the correct environment. (#1408)
37		-* Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents flows using code mappings from encountering errors when stopping their runtime while messages are still being processed. (#1550)
	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)
38	38
39		-====Remarks====
	30	+==== Bug fixes ====
40	40
41		-* New eMagiz Connector for Queues: The new eMagiz connector has been tested in Mendix with **Java 21**, and functionality works as expected.
	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.