Changes for page 266 - Feel Free

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-249 - Amendment Avalanche
	1	+266 - Feel Free

Content

...	...	@@ -1,35 +1,31 @@
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 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 Seperation.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>>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.266 - Feel Free.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 - 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	+* 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)
	11	+* Deploy - Release: Creating a new release automatically puts you in “edit mode” for that release. (#672)
	12	+* Create - Add Integrations: Improved how we autogenerate flows for the user.
	13	+* General - Platform: Improved our general deletion behavior when deleting a model.
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)
	17	+* 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]
	18	+* Manage - Monitoring - HTTP Statistics (Other metrics): The mean and max for the response time are split into two graphs. (#1200)
	19	+* Deploy - History: Entries stating 'null' will no longer be shown. (#1479)
	20	+* Manage - Monitoring - Log Entries: The search/reset buttons are disabled while the reset/search is still being processed. (#1538)
	21	+* Design - Edit an API integration - New/Edit resource: Added reserved keywords for the path of a resource, which can no longer be used. (#1585)
	22	+* Create - Transformation - Custom XSLT snippet: Trying to save a newly edited XSLT snippet is only possible in “Edit mode”. (#1670)
	23	+* 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)
	24	+* Design - Catalog: The default request body is generated automatically for the POST operation when added as an integration in the Design phase.
	25	+* Deploy - Architecture: Fixed an issue in the execution of the environment upgrade for models that have API MAM.
	26	+
	27	+==== Remarks ====
	28	+
	29	+* General - Infrastructure: An update has been applied to the internal communication with the eMagiz-managed authorization server.
	30	+* General - Infrastructure: 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.