Skip to Content

Changes for page 217 - Template Tango

Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 19.1
edited by Erik Bakker
on 2022/11/08 08:34
Change comment: There is no comment for this version
To version 84.1
edited by Erik Bakker
on 2023/05/26 08:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +198 - Great Migration
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 +Another couple of weeks have passed, so it is time for a new release. We have focused in this period on improving the migration process towards the next-generation architecture as well as how the user experience and interaction with the next-generation architecture works.
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.198 - Great Migration.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 also be opened from the Mapping and Data Model screens.
8 -** The Design Store now offers search options for store items, including Transformations and Data Models.
9 -** 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.
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 easier installation of multiple Store items with the same data model.
11 -
12 12  =====Minor changes=====
13 13  
14 -* 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.
15 -* Create - eMagiz Mendix Connector exit: Download buttons are added for non-legacy eMagiz Mendix connectors
16 -* 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.
7 +* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
8 +* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
9 +* Create - Flow designer: Added a validation for HTTP outbound gateways and HTTP outbound channel adapters that will create an alert if both Encoding mode and a REST template is set for the component.
10 +* Deploy - Releases: We improved the performance of preparing and deploying releases, by optimizing the algorithm that decides if runtime images needs to be rebuild or not.
11 +* Deploy - Releases: We improved resource validation when preparing releases. You will get notified when a flow resource was updated in one flow, but not in another flow in your release. Only applies to third generation runtimes.
12 +* Deploy - Architecture: When pressing "Apply to Environment" in Deploy -> Architecture there is no hard dependencies anymore on the (active) release when running in the next generation architecture. This makes it more clear and tangible what function is necessary for what goal.
13 +* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
14 +* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
17 17  
18 -
19 19  ====Bug fixes====
20 -* Design - Store: Importing store items from response messages doesn't cause issues anymore
21 -* Design - Store: Importing response messages and transformation to API integration is possible
22 -* Design - API Gateway: The order of attributes in gateway messages was sometimes different than in the generated Open API document.
23 -* Create - Flow Designer: Fix bugs when copying and pasting components in the G3 configuration
24 -* Create - Flow designer - Store: We fixed the maintaining selection of flow fragments from the store.
25 -* Manage - Exceptions of error messages: The count of error messages per exception class is now displayed (#744)
17 +
18 +* General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models.
19 +* Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
20 +
21 +====Remarks====
22 +
23 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.