Skip to Content

Changes for page 217 - Template Tango

Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 18.1
edited by Erik Bakker
on 2022/11/08 08:30
Change comment: There is no comment for this version
To version 53.1
edited by Erik Bakker
on 2023/03/03 08:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +193 - Fan Out
Content
... ... @@ -1,25 +1,23 @@
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.
1 +The release introduces REST/XML as option for your gateway operations as well as new features for our 3rd generation runtime, a new runtime image, and new cloud templates. Subsequently, we will release several minor feedback points and bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.187 - Integration Sponsor.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.193 - Fan Out.WebHome||target= "blank"]].
4 4  
5 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 11  
7 +* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V130.WebHome||target="blank"]].
8 +* Deploy - Releases: New release properties pop-up that shows all properties in your release, grouped by containers that they are assigned to. This pop-up can be accessed by pressing the wrench shaped icon, which becomes available once a release is set as active.
9 +* Design - Settings: We added XML support to API Management. To enable this feature, change the 'Default message format' in the Design settings section. You can change individual operations by changing the message format of your gateway message. Migrating existing operations requires a reset of the exit flow and a change in the catalog in Design. For more information see the release blog post. (#815)
10 +
12 12  =====Minor changes=====
13 13  
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.
13 +* Design - API Gateway: OData API type exclusively selectable for system admin. (#816)
14 +* Design - API Catalog: When you change a path in Design phase, your HTTP inbound gateways that use the changed path will also be updated in Create phase if you have edit rights. (#524)
15 +* Manage - Error messages: Message history is sorted by timestamp descending.
17 17  
18 -
19 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)
18 +
19 +* Create - Message Definition: Attribute can be declared as JSON array in API Gateway and Event Streaming (#908)
20 +* Create - Migration: We fixed a third generation migration issue, where the legacy error handling flow components were not removed from the asynchronous routing flow.
21 +* Create - Flow designer: when migrating a container’s flows from gen2 to gen 3, “global wire tap” components and their relevant components will be removed.
22 +* Deploy - Release: We fixed an issue that caused images to not be built in specific situations when running in the new runtime generation runtime.
23 +* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. (#797)