Changes for page 262 - Good News

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-186 - Daemon Switch
	1	+249 - Amendment Avalanche

Content

...	...	@@ -1,35 +1,35 @@
1		-The release brings the new monitoring stack to fruition and various updates to handling multiple namespaces. On top of that, we have released a slew of smaller feedback items and bug fixes.
	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.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.186 - Daemon Switch.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.249 - Amendment Avalanche.WebHome||target="blank"]].
4	4
5		-=====New features=====
6		-* Generic - New monitoring stack: As of this release, you can run on the new monitoring stack. For more information on becoming an early adopter, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	5	+==== New features ====
7	7
8		-=====Minor changes=====
	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. **
9	9
10		-* Design - Solution: You will see a warning in the Solution view on operation if it is not connected to a backend API operation or in "Transformation" mode.
11		-* Design - API Gateway: Changes in your Gateway messages are reflected directly in your OpenAPI JSON document.
12		-* Create - Flow Designer: You can now see who/when a resource was changed on a resource view page.
13		-* Create - Flow Designer: You can see all related configurations that use a specific resource when viewing the details of the resource.
14		-* Create - Flow Designer: Increased size of the SpEL expression input field of standard transformer component.
15		-* Create - Flow Designer: Show generated resources toggle is not disabled by default; your preference for showing or hiding generated resources will be saved.
16		-* Create - Flow Testing: The name of the starting point in the flow testing result tab is matched with the component type.
17		-* Create - Flow Testing: Added a button to display the content of a selected trace message in a pop-out.
18		-* Deploy - Releases: The automated flow test pop-up can now be closed by pressing "Enter."
19		-* Deploy - Properties: Password-type properties are masked in the unused properties pop-up.
20		-* Deploy - Properties: You can use enter key to search on the property overview page.
21		-* Deploy - User Management: "Generate Keystore" button is renamed "Download Keystore," and the file name contains environment information.
22		-* Administration - Licenses: Added event streaming storage usage of your models.
23		-* Model Dashboard - Going to manage from the model dashboard now loads the error message dashboard without having to click on the error messages dashboard explicitly
24		-* Store: Compatibility check is added, which prevents importing G3 store items into G2 flow/integration
25		-* General: Improved help texts explaining options and screens related to the new runtime architecture or the migration towards it.
	11	+==== Minor changes ====
26	26
27		-====Bug fixes====
28		-* Design - Integration Designer: For event streaming integrations, switching between Design Mapping and Create Transformation sometimes did not work.
29		-* Create - Transformation: For event streaming integrations, the 'Start editing' button sometimes did not work.
30		-* Create - Flow Designer: While editing an exit flow, the system message is not editable.
31		-* Create - Flow Designer: Comparing two flow versions works again.
32		-* Create - Flow Designer: When creating my initial version of a flow, the notification pop-up shows the correct information.
33		-* Create - Flow Designer: All relevant support objects will be highlighted when selecting a support object.
34		-* Deploy - Properties: Improved the layout of the cron trigger generator page
35		-* Deploy - Properties: Generating a password or CRON trigger will not reset the runtime field
	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)
	26	+
	27	+==== Bug fixes ====
	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)