Changes for page 262 - Good News

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-249 - Amendment Avalanche
	1	+262 - Good News

Content

...	...	@@ -1,35 +1,28 @@
1		-This release is characterized by many updates to our platform, both from a user perspective and from a technical perspective regarding our backend services. This sets us up to allow all users to prepare their Mendix systems for a migration to DSH (if applicable). Furthermore, it enables us to assist our users more effectively as they develop within the platform.
	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 have also launched a new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers. 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.249 - Amendment Avalanche.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.262 - Good News.WebHome||target="blank"]].
4	4
5		-==== New features ====
6		-
7		-* General - License Tracker: You can now see licensed flows on the model level alongside the company level after we have registered the correct configuration. (#859)
8		-* Event Streaming - DSH Connection: The eMagizConnector base image has been updated as preparation to support event streaming integrations on DSH. This allows all users to prepare their Mendix systems to connect to DSH.
9		-** Note that all users running the new eMagiz Connector will receive this update with their next release. **If you already have a running eMagiz Connector, you need to restart the application to retrieve the latest information after the new release is prepared for you. **
10		-
11	11	==== Minor changes ====
12	12
13		-* Event Streaming - User Management: When adding new event streaming integrations that link to an **existing** event streaming processor, you **must** transfer them to the Create phase via the adding integrations tooling in the Create. This will trigger eMagiz to update the Deploy user management accordingly.
14		-** This functionality applies to both the old and new event broker.
15		-* Design - Message Definition: The overview of the attributes shown in the entity overview of the data model (i.e., CDM) and the system message now also shows the description of the attribute. (#1671)
16		-* Create - Flow Designer: The circuit breaker option under the request handler advice chain can now also be filled with a property placeholder. (#1619)
17		-* Create - Flow Designer: The overwrite option of the headers of a standard header enricher is now placed in the 'Basic' tab instead of the 'Advanced' tab. (#1666)
18		-* Create - Flow Testing: When creating a new test message and selecting the option "from existing file", the default option is now "Create" instead of "Capture". (#1659)
19		-* Create - Flow Testing: Each trace entry in the "Traces" overview now contains a timestamp. (#1661)
20		-* Capture - Overview: Deleting systems/integrations/tenants in Capture now shows a progress bar. (#1665)
21		-* Deploy - Unused Properties: For the unused properties functionality on the Create Phase Release, it is adjusted so that only the properties that are not used in any of your releases across environments are shown. They can be deleted without impacting any of the existing releases. (#1244)
22		-** Context is added to guide users through the following actions.
23		-** Performance has improved significantly. As a result, the process takes less time than before.
24		-* Deploy - Releases: Promoting a release to the next environment does not trigger the auto-delete behaviour of releases anymore. (#1318)
25		-* Deploy - Containers: Only the active containers are updated when a user adds or removes something from a release. Consequently, when a new integration is added, inactive containers will not contain the new integration. They can be reactivated if desired to enable automatic updates again. (#986)
	7	+* General - Runtime Image: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers is available.
	8	+* Create - Flow Designer: The help text for the Result Type attribute of the JSON to XML transformer has been improved. (#1553)
	9	+* Deploy - Releases: The on‑hover text for a release also displays the most recent date and time the release was edited. (#341)
	10	+* Create - Flow Designer: Unused support objects can be deleted with a single button. (#794)
	11	+* Deploy - User Management: For models that have been migrated to our latest functionality for both our event streaming and API offering, changes to users in the Deploy phase will be applied immediately for both manually created users and system users.
	12	+* Deploy - Architecture: The Apply to Environment pop-up has been updated to reflect progressive changes made to specific objects. Any pending changes on Container, Router, Certificate, Instance, and AWS resources are now stacked and displayed to the user. The list is ordered from the earliest change at the top to the most recent at the bottom, allowing users to clearly see all modifications made to a specific object until the Apply to Environment button is clicked. These changes will remain active for future operations. (#1537)
	13	+* Deploy - Architecture - Routes: The View and Edit pages for Routers have been updated to remove the Endpoint DNS Name and Flow Symbolic Name fields. (#1537)
	14	+* Manage - Alerting: For Log and Error triggers, a custom subject can now be specified under ‘notifications’. This enables you to sort incoming alerts in your mailbox more easily.
	15	+* Manage - Alerting: We have tightened the allowed characters for the triggers to reduce further the likelihood of HTML injection into the bodies of alerting emails sent by eMagiz.
	16	+** Note: if you already have existing alert rules that contain characters that are now considered illegal, you will need to change them when you make any change to that trigger.
26	26
27	27	==== Bug fixes ====
28	28
29		-* Create - Add Integrations: We fixed several issues regarding untransferring and transferring integrations. Among other things, we addressed the following specific cases.
30		-** Re-transferring integrations to Deploy.
31		-** Untransfering the last integration of a system.
32		-* Create - Flow Designer: The user can now completely read the alerts in the flow designer with a hover text. (#1168)
33		-* Create - Flow Designer: The "Allow empty array" checkbox in Create can now be used without it throwing an error. (#1640)
34		-* Create - Flow Designer: We ensured that the order in which you create flow versions for flows belonging to an "exit/entry" construction can be random. As a result, this will prevent users from ending up with only a part of the flows belonging to this construction in Deploy, while all flow versions are indeed created in Create.
35		-* Manage - Alerting - Triggers (Error): Error alerts with ‘not equal to’ and ‘does not contain’ evaluations on ‘exception class’ and/or ‘exception message’ will now only trigger if both the first and last exception don’t equal/contain the value. (#1576)
	20	+* Create - Flow Designer: When using DSH support objects, the required admin-only fields are automatically filled in. (#1755)
	21	+* Create - Untransfer integration: We fixed an issue where you could not remove an integration of the Mendix connector system, which was migrated from the Legacy eMagiz Mendix Connector to the current eMagiz Mendix Connector in Create.
	22	+* Design - Catalog: Help texts related to “content”, “Json format”, and “Gateway message definition” are updated. (#1082)
	23	+* Create - Store: When importing a store component with properties, validation feedback will now be provided if the property value does not align with the expected type. (#1276)
	24	+* Manage - Explore: Error message is much more descriptive when the container is not running (#1321)
	25	+
	26	+==== Remarks ====
	27	+
	28	+* General - Infrastructure: We updated our image builder for Windows images to use the latest Java versions for images. Effectively, this means that any image built for Windows from this release onwards that uses a base image //3.4.0// or above, will use Java 21.0.10 as baseline. Images below version //3.4.0// will now use Java 17.0.18. Therefore, new (property) releases that use the same eMagiz base image, will still use a different Java version, and may therefore have some changed behavior. Normally that would not be noticable, but since these Java version increases drops support for some weak cipher suites, connectivity may be affected. For more information, please refer to the release notes of image 3.5.1.