Changes for page 256 - Power Up

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-196 - The Last Post
	1	+249 - Amendment Avalanche

Content

...	...	@@ -1,39 +1,35 @@
1		-Here is our first release of this quarter. We have delivered additional minor (bug) fixes in this release and released the Live Flow testing feature. The last is a real improvement during the development process of a flow. Furthermore, you will find several enhancements in working in nextGen environments.
	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.196 - The Last Post.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		-* Create - Flow Testing: Till now, Flow Testing allowed to test eMagiz flows by defining a testing point on the start (and end) point(s), running them, and comparing the actual and expected messages. In this release, "Live Mode Testing" is introduced, making testing communication with an actual "live" endpoint possible. As a result, an "HTTP outbound gateway" can be set in "Live Mode." When you do this, the HTTP outbound gateway will send its request to the endpoint. Consequently, the response will be handled by the flow in the flow test so you can determine whether the actual endpoint behaves as expected.
	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. **
8	8
9		-=====Major changes=====
	11	+==== Minor changes ====
10	10
11		-* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target= "blank"]] for more information.
	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)
12	12
13		-=====Minor changes=====
	27	+==== Bug fixes ====
14	14
15		-* Design - Store: You can encounter a warning message when you import a transformation from the store because your imported transformation requires information from the related store fragment. To avoid a non-functional transformation in the Create phase, you should include that store fragment. Afterward, we will update your default flow component transformer to make it work correctly.
16		-* Design - Store: We updated importing to help you avoid an error while importing store items that will break your message definition in some cases.
17		-* Design - Store: We fixed an issue that you import the message definition(s), and a specialized DataType of imported message definition(s) is not matched with the exported message definition(s). Now, they are matched, and your transformation won't get issues.
18		-* Create - Store: We automatically excluded resources that are not good enough from the exporting wizard. Then you will find it easy to recognize a problem and avoid creating unusable store items.
19		-* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can only change the CDM message definition, Gateway message definition, or even Event streaming message definition with the proper rights. (#690)
20		-* Create - Flow designer: Model resources tab removed on the resources page when adding a resource to a validating filter. (#921)
21		-* Create - Flow designer: Improve the responsiveness of the resources tab on the right panel.
22		-* Create - Flow Designer: Resources in the "Unused resources" section can be marked as used when components refer to the resources through property placeholders or in custom SPeL expressions.
23		-* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests if that parameter was not supplied, so please reset your entry flow to apply the fix.
24		-* Create - API Gateway: We fixed an issue where API-Key secured requests would fail with error code 500 instead of code 401 if no API-Key was supplied. Please reset your entry flow to apply the fix.
25		-* Create - Resources: When viewing a resource, its full name will be shown, removing the need to download the resource to obtain its name. (#922)
26		-* Deploy - Releases: We reduced the time it takes to prepare a release before it can be deployed. The process of building runtime images has been optimized.
27		-* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
28		-* Deploy - Architecture: The topics are now ordered alphabetically, and the runtimes will now get the same order as design architecture (after 'apply to environment') (#543)
29		-* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are run.
30		-* Manage - Explore: A new queue delete button is added. This button is only visible to authorized personnel.
31		-* Administration -User management: Company contact can edit permissions of models that fall under child companies. (#895)
32		-* Administration - Overview: Contracts page removed. (#907)
33		-
34		-====Bug fixes====
35		-
36		-* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They better explain what you need them for and mention essential security considerations.
37		-* Create - Flow designer: Various minor (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
38		-* Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514)
39		-* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.
	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)