Changes for page 249 - Amendment Avalanche

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-241 - Wild West
	1	+249 - Amendment Avalanche

Content

...	...	@@ -1,41 +1,35 @@
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 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.241 - Wild West.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====
	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	+* 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		-====Minor Changes====
	11	+==== Minor 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	+* 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)
19	19
20		-====Bug fixes====
	27	+==== Bug fixes ====
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)
38		-
39		-====Remarks====
40		-
41		-* New eMagiz Connector for Queues: The new eMagiz connector has been tested in Mendix with **Java 21**, and functionality works as expected.
	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)