Changes for page 262 - Good News
Last modified by Erik Bakker on 2026/02/23 08:06
From version 64.1
edited by Erik Bakker
on 2023/04/11 10:07
on 2023/04/11 10:07
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 195 -EasterParty1 +255 - Fine Form - Content
-
... ... @@ -1,30 +1,21 @@ 1 - Asthe quarter hasended,wewentsilentforacoupleof weeks to planfor theupcomingquarterduringourPI rituals.This time weaddedthefamous"Hackathon"tothe end ofthe PI week sowe could starttheEaster breakwithexcellent spiritaftersolving several smaller feedbackitems and bugsreported by you.Severalofthosestories will beincluded in this and the upcomingrelease.On top of that, we introduce variousimprovementsto ourAPI Gatewaypattern andour 3rdgenerationruntimearchitecture. Subsequently, we will release a new runtime imagesupporting the multipleimprovements.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. 195 -EasterParty.WebHome||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 -==== =Minor changes=====5 +==== Minor changes ==== 6 6 7 -* General - Control Tower: Changed several generic triggers for more predictable behavior. 8 -* Administration - License Tracker: The license tracker has been updated for new license models and features. 9 -* Administration - License Tracker: When the feature ‘Data sink’ is enabled, the number of message packs of the contract will be displayed when you hover with the mouse over the feature. 10 -* Capture - Settings: Editing message types are now consistent between new and existing ones. (#884) 11 -* Design - API Gateway: Default HTTP responses are generated automatically (#417) 12 -* Design - Solution design: An additional option is added to the context menu that navigates to the message definition added to event streaming topics without processors. (#850) 13 -* Create - Add Integrations: We used the name of the API integration that you set in the Design phase to display on the Transfer screen. That helps you choose the correct integrations to add to the Create phase more quickly. 14 -* Create - 3rd Generation Migration: You can toggle the custom error handling option for your event processors while migrating your event processing container to the 3rd Generation Runtime. 15 -* Deploy - Deployment plan: When you run your deployment plan in your model using the new generation runtimes, you will be able to be the logs that relate to an executing deployment step. 16 -* Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan. 17 -* Deploy - Architecture: Certificates only editable by system admin. 18 -* Manage - Jobs: In case the model has containers that contain jobs in one of its flows, users can inspect job managers, job executions, and job step executions. Note that this only works for the 3rd generation runtime. 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) 19 19 20 -====Bug fixes==== 13 +==== Bug fixes ==== 21 21 22 -* General-RuntimeImage:Anewruntimeimageforcustomermodels running onthe3rdgeneration runtime. Pleaselearnmoreaboutour [[Runtime Image releasenotes>>Main.ReleaseInformation.RuntimeImages.V140.WebHome||target="blank"]].23 -* Design - API Gateway:Improvedgenerationof OpenAPI JSON and example messages forAPIgateway operations tohandlecaseswhereanelementinyourgatewaydefinitionis usedmultipletimes. (#440)24 -* Design-API Gateway:Wefixedanissuewherechangingthe messageformat ofagatewaymessagedidnot result inan updateoftheOpenAPI(i.e., Swagger)document.25 -* Design- System message: Wefixedanissuethatled toimportingtowards thewrongmessagedefinitionwhenthe option"ImportfromXSD"waschosenonasynchronousmessage.(#818)26 -* Create- Message:Whenviewingor editinganenumeration, itis nolongerdeletedwhenthecancelbuttonispressed.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 27 27 28 -====Remarks==== 29 29 30 -* Deploy - Releases: We removed the existing snapshots of release property values.