Changes for page 208 - Controlled State
Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 154.6
edited by Danniar Firdausy
on 2023/11/07 11:51
on 2023/11/07 11:51
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 208 - ControlledState1 +188 - Close Encounters - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.ebakker - Content
-
... ... @@ -1,27 +1,25 @@ 1 - In the lastsprintcycle, we focused on deliveringmonitoringfunctionalityforthestategenerationcomponents. On top of that, we alsomadeseveral improvementsonthecomponentsinterfacingtheusers toimprovetheuser experienceaspect ofour platform. Moreover, wemade somebugfixes and improvementson releases inDeploy andmonitoring in Manage.1 +The release brings several improvements to our 3rd generation runtime and the interaction with it. On top of that, we have several feedback items and bug fixes. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 208 - ControlledState3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.188 - Close Encounters.WebHome||target="blank"]]. 4 4 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. 11 + 5 5 =====Minor changes===== 6 6 7 -* Design - Message Mapping: The button 'Import from Store' will directly open the store. 8 -* Create - Flow Designer: Performance improvements for the Flow Designer have been implemented. 9 -* Deploy - Releases: During removing a release, users will be informed about the environments and the runtimes in which the release under deletion is running. 10 -* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well. 14 +* Create - Flow Designer: Code mapping is now available for models migrating to the 3rd generation runtime 15 +* Create - eMagiz Mendix Connector exit: Download buttons are added for non-legacy eMagiz Mendix connectors. 16 +* Create - Overview: You will now see your errors within a flow but on the Create - Overview. To activate this, open your flow, and the number of errors you have in it, if any, will update so that next time, you don't have to navigate inside the flow to check how many alerts you have. 11 11 12 12 13 -* Manage - Monitoring: There is a new page called the "State generation statistics" that is located right under the Topic statistics navigation menu, which is only shown and accessible for models that has the add-on license for state generation. 14 -* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched. 15 -* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022) 16 - 17 17 ====Bug fixes==== 18 - 19 -* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055) 20 -* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused. 21 -* Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087) 22 -* Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term. 23 - 24 - 25 -=====Infra and image changes===== 26 - 27 -* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information. 20 +* Design - Store: Importing store items from response messages doesn't cause issues anymore. 21 +* Design - Store: Importing response messages and transformation to API integration is possible. 22 +* Design - API Gateway: The order of attributes in gateway messages was sometimes different than in the generated Open API document. (#783) 23 +* Create - Flow Designer: Ensure that the copy and pasting experience works for all flows. 24 +* Create - Flow Designer - Store: We fixed the maintaining selection of flow fragments from the store. 25 +* Manage - Exceptions of error messages: The count of error messages per exception class is now displayed. (#744)