Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/05/22 13:37

From version 157.1
edited by Danniar Firdausy
on 2023/11/07 13:08
Change comment: There is no comment for this version
To version 21.1
edited by Erik Bakker
on 2022/11/08 09:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -208 - Controlled State
1 +187 - Integration Sponsor
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -1,23 +1,29 @@
1 -In the last sprint cycle, we focused on providing users with a monitoring functionality for the state generation components. On top of that, we also made several improvements to the components interfacing the users to improve the user experience aspect of our platform. Moreover, we made some bug fixes and improvements on releases in Deploy and monitoring in Manage.
1 +The release brings the next step of the Design store to the public and releases a new version of the eMagiz Mendix Connector that unlocks those using it to migrate to the next generation runtime. 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 - Controlled State .WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.187 - Integration Sponsor.WebHome||target="blank"]].
4 4  
5 -=====Minor changes=====
5 +===== Runtime Release Notes =====
6 6  
7 -* Create - Flow Designer: Input fields for XPath expressions have been made wider and capable of expanding to facilitate longer inputs. (#822)
8 -* Create - Flow Designer: Small styling changes and bug fixes have been implemented for edge cases during editing channels in the Flow Designer.
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. (#1060)
10 -* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
11 -* Deploy - Deployment: The “preparing” step of the release at the beginning of the deployment is now faster due to the improved process of building the images.
12 -* Manage - Monitoring: There is a new page called "State generation statistics" that is located right under the Topic statistics navigation menu, which is only shown and accessible for models that have the add-on license for state generation.
13 -* Manage - Error messages & Log entries: Searching on entries now supports phrase matching, meaning that users can search entries based on phrases containing two or more words and entries with distances of 2 or incomplete search phrases.
14 -* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
15 -* All - Toggles: We updated all instances of the toggle switch in the platform due to the latest eMagiz Design System module implementation in our platform.
16 -* All - Error Channel: Added a migration step in Gen3 migration, we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
7 +The 6.0.0 release of the eMagiz Mendix connector (EMC) is here. This eMagiz Mendix connector (EMC) version is compatible with the 3rd generation runtime. On top of that, it includes updates on most of the userlib libraries to have the latest security fixes in place. For specific information, please check out this link to the [[release notes>>Main.Release Information.Runtime.eMagiz Mendix Connector - 600.WebHome||target="blank"]].
17 17  
18 -====Bug fixes====
9 +=====New features=====
10 +* Design - Store: It is now possible to import Transformations and Data Models from the store into a model.
11 +** The Design Store can also be opened from the Mapping and Data Model screens.
12 +** The Design Store now offers search options for store items, including Transformations and Data Models.
13 +** 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.
14 +** 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.
19 19  
20 -* Deploy - Deployment: We fixed an issue that the deployment plan got stuck or stopped randomly sometimes.
21 -* Deploy - Deployment: We resolved an issue where sometimes older containers get deployed, while eMagiz shows the new containers are deployed.
22 -* Manage - Monitoring: Improved message processing in infra components that should reduce the occurrence of log messages failing to be sent in Gen3 models.
16 +=====Minor changes=====
23 23  
18 +* Create - Flow Designer: Improved the help texts of the Kafka components to explain specific performance and load-balancing considerations better and added detailed information on how messages (including headers) are converted to/from Kafka records.
19 +* Create - eMagiz Mendix Connector exit: Download buttons are added for non-legacy eMagiz Mendix connectors.
20 +* 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.
21 +
22 +
23 +====Bug fixes====
24 +* Design - Store: Importing store items from response messages doesn't cause issues anymore.
25 +* Design - Store: Importing response messages and transformation to API integration is possible.
26 +* Design - API Gateway: The order of attributes in gateway messages was sometimes different than in the generated Open API document.
27 +* Create - Flow Designer: Fix bugs when copying and pasting components in the G3 configuration.
28 +* Create - Flow Designer - Store: We fixed the maintaining selection of flow fragments from the store.
29 +* Manage - Exceptions of error messages: The count of error messages per exception class is now displayed. (#744)