Changes for page 256 - Power Up
Last modified by Erik Bakker on 2025/11/04 12:44
From version 287.1
edited by Erik Bakker
on 2025/10/21 10:20
on 2025/10/21 10:20
Change comment:
There is no comment for this version
To version 112.1
edited by CarlijnKokkeler
on 2023/10/11 12:53
on 2023/10/11 12:53
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 55-FineForm1 +206 - Situational Deployment - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,21 +1,26 @@ 1 - Thisrelease featuresvariousupdatesto our platform, with a user-centricfocus, as wework onwrapping up improved functionalityfor ournew event streaming broker. All those improvementswill be sharedin thefutureonce everything is ready. Additionally, wewill releasea new **[[runtimeimage>>Main.ReleaseInformation.RuntimeImages.V340.WebHome||target="blank"]]**forselectedcustomers and on our flow testing engine.1 +In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store. 2 2 3 -Please find out more on our [[Release blog>> doc:Main.Release Information.Release Blogs.255-FineForm.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Situational Deployment.WebHome||target="blank"]]. 4 4 5 -==== Minor changes====5 +=====New features===== 6 6 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) 7 +* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information. 12 12 13 -==== Bugfixes====9 +=====Minor changes===== 14 14 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 11 +* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration. 12 +* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869) 13 +* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1042) (#1046) (#1052) 20 20 21 21 16 +====Bug fixes==== 17 + 18 +* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054) 19 +* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes. 20 +* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed. 21 +* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues. 22 + 23 + 24 +=====Infra and image changes===== 25 + 26 +* No infra and/or image changes is this release.