Changes for page 220 - Patch Parade
Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 97.1
edited by Erik Bakker
on 2023/07/17 15:25
on 2023/07/17 15:25
Change comment:
There is no comment for this version
To version 18.1
edited by Erik Bakker
on 2022/11/08 08:30
on 2022/11/08 08:30
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 - 201 -BeInformed1 +187 - Integration Sponsor - Content
-
... ... @@ -1,30 +1,25 @@ 1 - In the lastsprintcycle,wefocusedonplanningahead,finishingupandworking ontheHackathon to fixseveralsmalleritems.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. 201 -BeInformed.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.187 - Integration Sponsor.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 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. 11 + 5 5 =====Minor changes===== 6 6 7 -* Portal - Menu: the back button is changed to have text so it shows clearer the navigation target. (#949) 8 -* Design-Architecture: Topic Storage detail page contains help text. (#994) 9 -* Design - API Endpoint Specification: Improved UI and added independent scroll functionality. (#832) 10 -* Design - API Gateway: Small styling improvements to the edit integration page. (#954) 11 -* Create - Flow Designer: When deleting one or multiple components, you will not be able to change the selection before confirming or cancelling the delete action. (#969) 12 -* Create - Migrate to 3rd Generation: In the event one or more flows break during migration, a popup will inform the fows containing errors after migration is finished. (#983) 13 -* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to environment. (#979) 14 -* Deploy-Architecture: Upon pressing the button “Apply to environment”, a confirmation page is shown. Here all changes made in the portal that will have an effect in your running environment are listed. These changes can be applied to environment or reverted. (#828) 15 -** Changes made in Deploy Architecture with an effect to your running environment will only be listed when they are made after this release. 16 -** Changes with a direct effect will not be listed (for example restarting a machine). 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. 17 17 18 -====Bug fixes==== 19 19 20 -* Design - Solutions: We fixed an issue that a message mapping error is displayed despite having a passthrough API gateway. (#935) 21 -* Design - Settings: The full length of the contract number can now be registered. (#958) 22 -* Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen3 will not block migration. (#982) 23 -* Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into you runtimes. (#990) 24 -* Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double click on a user to open its details. (#972) 25 -* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964) 26 - 27 -=====Infra and image changes===== 28 - 29 -* Changed the endpoint that is used for sending errormessages to the eMagiz Control Tower. 30 -* Updated the Spring version of the gateway supporting deploy and manage phase operations. 19 +====Bug fixes==== 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)