Changes for page 189 - Private Eye

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

From version 9.1
edited by Erik Bakker
on 2022/10/14 13:54
Change comment: There is no comment for this version
To version 17.1
edited by Erik Bakker
on 2022/11/08 08:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - Get Ready
1 +187 - Integration Sponsor
Content
... ... @@ -1,24 +1,25 @@
1 -Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities.
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.185 - Get ready.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.187 - Integration Sponsor Switch.WebHome||target="blank"]].
4 4  
5 5  =====New features=====
6 -* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file.
6 +* Design - Store: It is now possible to import Transformations and Data Models from the Store into a model.
7 +** The Design Store can now be opened from the Mapping and Data Model screens as well.
8 +** The Design Store now offers search options to find store items that include Transformations and/or Data Models.
9 +** When importing a Store item with a Transformation and/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 for easier installation of multiple Store items with the same data model.
7 7  
8 8  =====Minor changes=====
9 9  
10 -* Design System. Changed the look and feel across the portal altogether. Changes can be seen in:
11 - ** Datagids, where there is now on hover action for example.
12 - ** Pop ups
13 - ** Context menus, also have on hover action
14 - ** Styling of scrollbars
15 -* Message Redelivery - admin logs improved to better analyze issues when they occur
16 -* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality
17 -* Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed
14 +* Create - Flow designer: Improved the help texts of the Kafka components to better explain certain performance and load-balancing considerations, and added detailed information how messages (including headers) are converted to/from Kafka records.
15 +* Create - eMagiz Mendix Connector exit: Download buttons are added for non legacy eMagiz Mendix connectors
16 +* Create - Overview: You will now be able to see the errors that you have within a flow but on the integration widget. To do this, go into 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.
18 18  
18 +
19 19  ====Bug fixes====
20 -* Deploy - Deployment plan. Performance of page to deploy a release increased significantly
21 -* Store - Import resources was incorrectly done in specific cases, which is now fixed
22 -* Store - Target namespace will be imported when importing an XML Message Definition
23 -* Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model.
24 -* Store - Importing items from the store sometimes resulted in invalid JMS connection factories.
20 +* Design - Store: Importing store item from response messages doesn't cause issues anymore
21 +* Design - Store: Importing response message and transformation to Api integration is possible
22 +* Design - API Gateway: The order of attributes in gateway messages were not always the same as the order in the generated Open API document.
23 +* Create - Flow Designer: Fix bugs when copy and paste components in G3 configuration
24 +* Create - Flow designer - Store: We fixed the maintaining selection of flow flagment from Store.
25 +* Manage - Exceptions of error messages: The count of error messages per exception class are now displayed (#744)