Changes for page 256 - Power Up

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-217 - Template Tango
	1	+255 - Fine Form

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.CarlijnKokkeler
	1	+XWiki.ebakker

Content

...	...	@@ -1,17 +1,21 @@
1		-In the last sprint cycle, we focused on delivering new cloud templates for docker single and docker double lane. Moreover, we have added clipboard buttons to several pages, and migrated the generic alert trigger "More than 100 messages on queue over 10 minutes" to a dynamic trigger. Lastly, we enabled the removal of eMagiz infra H2 databases for connector machines, and improved the checks on the runtime versions in the runtime overview.
	1	+This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready. Additionally, we will release a new **[[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]]** for selected customers and on our flow testing engine.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.217 - Template Tango||target="blank"]].
	3	+Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.255 - Fine Form.WebHome||target="blank"]].
4	4
5		-=====New features=====
	5	+==== Minor changes ====
6	6
7		-* Create - Flow Designer & Deploy: Copy to clipboard buttons have been added to various pages.
8		-* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce the ability to clean H2 databases from the portal. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9		-* Manage - Alerting: The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger.
	7	+* General - Runtime: A new [[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]], for selected customers, and our flow testing will be made available.
	8	+* General: The user can now see the names of deactived users again across the platform (i.e. flow history, Q&A). (#1163)
	9	+* Deploy - Releases: We have updated the editing release behaviour for the Event streaming pattern. You now have more flexibility for you to add or remove either Event streaming processor flow(s) or Event streaming Mendix connector flow(s) in the release.
	10	+** Additionally, we have also fixed the issue where adding or removing event streaming flow(s) resulted in incorrect flow(s) being included or excluded. This update ensures that the correct Event streaming flow(s) are now properly managed during release editing.
	11	+* Create - Add Integrations: Users can un-transfer event streaming integrations that have the default message type messaging by using the ‘Create/Settings/Transfer settings from design/ES Integrations’. (#1485)
10	10
11		-=====Minor changes=====
	13	+==== Bug fixes ====
12	12
13		-* Deploy - Architecture: For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note that only H2 databases that are registered under the standard eMagiz data folder will be removed. Moreover, it is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. Lastly, for on-premise runtimes, only a reset of the runtime is needed.
	15	+* Design - Model Designer: Changed “align top“ and “align left“ to “align horizontally“ and “align vertically“ to be consistent with similar functionality in the Flow Designer. (#1611)
	16	+* Create - Settings: The SOAP settings tab allows syncing the SOAP settings of systems in Design and Create. (#1569)
	17	+* Create - Transformation: Updated the pattern used in dateTime transformations for the +HH:mm format. These used to fall back to +HHmm instead (dropping the ':'), this has now been resolved. (#1368)
	18	+** Existing transformations are not automatically updated, but if you are using a custom XPath to do the transformation right now, you can now use the default functionality again.
	19	+** The updated pattern (using XXX instead of ZZ) does not work on the previous generation runtime. If you are still using the previous generation runtime, and you have edited the specific part of the transformation, you can instead use the custom XPath where you use the pattern that is composed when using the dropdown menus, and replacing the XXX at the end with ZZ
14	14
15		-====Bug fixes====
16	16
17		-* Deploy - Runtime Overview: The runtime overview has been improved with respect to checks on the runtime version. (#1243)