Changes for page 217 - Template Tango

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

From version 21.1
edited by Erik Bakker
on 2022/11/08 09:01
Change comment: There is no comment for this version
To version 58.1
edited by Erik Bakker
on 2023/03/14 08:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +194 - Giant Leap
Content
... ... @@ -1,29 +1,33 @@
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 various improvements on our 3rd generation runtime architecture and various other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements.
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.194 - Giant Leap.WebHome||target= "blank"]].
4 4  
5 -===== Runtime Release Notes =====
6 -
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"]].
8 -
9 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.
15 15  
7 +* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V131.WebHome||target="blank"]].
8 +* Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers and waking up a cloud slot will start those containers. (#889)
9 +
16 16  =====Minor changes=====
17 17  
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.
12 +* Create - 3rd generation runtime migration: When migrating your event streaming container to the 3rd generation runtime, the event streaming infra flow will be updated correctly based on whether you are using custom error handling on your event processors or not.
13 +* Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807)
14 +* Deploy - User Management: Roles are sorted alphabetically. (#806)
15 +* Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup. Please use the ‘Upgrade’ feature to keep your cloud architecture up-to-date.
16 +* Manage - Event Streaming Statistics: Updated graphs to display the average of the selected timeframe, added help texts to each table and graph and made some small visual improvements.
17 +* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833)
21 21  
22 -
23 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)
20 +
21 +* Generic: We fixed an issue that you may see a screen with a broken styling when switching among phases.
22 +* Create - Flow Designer: Removed the option to create a new resource on resource selection pop-up of simple XSD schema support object.
23 +* Create - Flow designer: We fixed the flow generation of entry flows for API Key secured API Gateway operations. This problem was introduced in version 193 (2023-02-04). (#902)
24 +* Create - Resources: We fixed an issue when deploying flows with uploaded resources with very long filename (>100 characters).
25 +* Deploy - Releases: You need edit rights in test environment of deploy phase to execute “Update flows to latest versions” action.
26 +* Manage - Dashboard: We update the view to visualize the split entries after you do a migration a combined entries.
27 +* Manage - Logging: When a container cannot be started due to an incorrect stylesheet, the error message will include what the error is and in which stylesheet is occurred (#825)
28 +* Manage - Logging: Reduced the occurance of 'Failed to send to Elastic' log messages which triggers alerts. (#898)
29 +* Manage - Alerting: Editable column shows the correct value.
30 +
31 +====Remarks====
32 +
33 +* Create - Flow designer: After the deployment, the ‘Version Compare' and 'Version Restore’ features will be unavailable for a few hours, because of data migration. You will get an error stating that the version is not compatible with the selected feature until migration has finished.