Changes for page 220 - Patch Parade
Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 102.1
edited by Erik Bakker
on 2023/08/15 12:23
on 2023/08/15 12:23
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 - 203-FastPaced1 +187 - Integration Sponsor - Content
-
... ... @@ -1,19 +1,25 @@ 1 - In the lastsprintcycle,wefocusedonthescalabilityand stabilityofourinfrastructure. On top of that, wewill release severalminor changeswithapotentiallysignificant impact.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. 203-FastPaced.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 -* Create - Integrations: Improved the performance of adding or removing API gateway integrations for split entry configurations. (#1023) 8 -* Manage - Alerting: Identifiers of triggers are now visible in the edit screen. 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. 9 9 10 -====Bug fixes==== 11 11 12 -* Create - Flows: Fixed an issue where removing some split entry flows from Create phase was not possible after splitting your all entry/combined entry flow. (#1016) 13 -* Deploy - Releases: We fixed an issue that your release contains a JMS server flow twice with different build version numbers when adding another flow to your release. (#597) 14 -* Deploy properties: When a user activates a release containing nested properties and the property is not created, we show it now as missing. On top of that, we add the property placeholder after the user tries to activate the release. 15 - 16 -=====Infra and image changes===== 17 - 18 -* Infrastructure: Tightened security policies for a more secure infrastructure. 19 -* Infrastructure: Added and improved auto-scaling behavior for the eMagiz Control Tower 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)