Changes for page 220 - Patch Parade
Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 23.1
edited by Erik Bakker
on 2022/11/21 13:13
on 2022/11/21 13:13
Change comment:
There is no comment for this version
To version 77.1
edited by Erik Bakker
on 2023/05/09 13:55
on 2023/05/09 13:55
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 -1 88-CloseEncounters1 +197 - Pay Attention - Content
-
... ... @@ -1,25 +1,21 @@ 1 - Theeleasebrings severalimprovementstoour3rdgeneration runtime and theinteractionwithit.On topofthat, wehaveseveralfeedback itemsandbugfixes.1 +Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. Furthermore, you will find several enhancements in working in nextGen environments. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.1 88-CloseEncounters.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.197 - Pay Attention.WebHome||target= "blank"]]. 4 4 5 5 =====New features===== 6 -* Design - Store: It is now possible to import Transformations and Data Models from the store into a model. 7 -** The Design Store can also be opened from the Mapping and Data Model screens. 8 -** The Design Store now offers search options for store items, including Transformations and Data Models. 9 -** When importing a Store item with a Transformation or Data Model, a new merge tool is available to link the Store Items data model to the users' data model or to add new attributes/entities to the user data model. 10 -** When importing a Store item with a data model that has been previously linked, the links are automatically restored, allowing for easy updating of store-based Integrations and easier installation of multiple Store items with the same data model. 6 +* 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. 7 +* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support. 11 11 12 12 =====Minor changes===== 13 13 14 -* Create - Flow Designer:Codemappingisnow availablefor modelsmigratingto the3rdgenerationruntime15 -* Create-eMagiz MendixConnector exit:Downloadbuttons are addedfornon-legacyeMagizMendixconnectors.16 -* Create-Overview:Youwillnow see yourrrorswithin a flow but on theCreate - Overview. To activatethis, open yourflow, andthe number oferrorsyouhave in it,if any,willupdateothat nexttime,youdon'thavetonavigate inside the flow to check how many alertsyou have.11 +* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated. 12 +* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute." 13 +* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments. 17 17 18 - 19 19 ====Bug fixes==== 20 - * Design - Store: Importing store items from response messages doesn't cause issues anymore.21 -* Design- Store:Importingresponse messagesand transformationtoAPIintegrationispossible.22 -* De sign- API Gateway: The orderof attributesingatewaymessageswassometimesdifferentthaninthegenerated OpenAPIdocument.(#783)23 -* Create - FlowDesigner:Ensure thatthecopyandpastingexperienceworksforall flows.24 -* Create - FlowDesigner-Store:Wefixedthemaintainingselection offlowfragmentsfrom the store.25 -* Manage- Exceptionsoferror messages:Thecountferror messagesperexceptionclassisnowdisplayed. (#744)16 + 17 +* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item. 18 +* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. 19 +* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture. 20 +* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again. 21 +* Design - Message Definitions: "Message format" button is also available in view mode. (#919)