Skip to Content

Changes for page 256 - Power Up

Last modified by Erik Bakker on 2025/11/04 12:44
From version 283.1
edited by Erik Bakker
on 2025/10/09 09:19
Change comment: There is no comment for this version
To version 82.1
edited by Erik Bakker
on 2023/05/22 15:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -254 - Other One
1 +198 - Great Migration
Content
... ... @@ -1,22 +1,27 @@
1 -This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready. Additionally, we will release new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** to update our underlying libraries.
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>>doc:Main.Release Information.Release Blogs.254 - Other One.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 -==== Minor changes ====
5 +=====New features=====
6 6  
7 -* General - Cloud Template: A new [[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]], for every type of **cloud** we offer, is available that updates underlying libraries.
8 -* General - eMagiz Store: Introduced a new state generation license type for store items. This license is now required for models intending to utilize store items that depend on state generation capabilities. (#1400)
9 -* Capture - Settings - Integrations: Update column label to be more consistent (#1710)
10 -* Design - Data model: When you change the data type of the attribute in the Design phase while a flow has a transformation in Create, before saving the changes, you will see the confirmation popup with the warning message because the changes will impact your transformation in Create. (#1163)
11 -* Create - Flow testing: Specifying the type of a header on a test message has been made simpler: Instead of having to type the class name, the most common types can now be selected in a dropdown menu instead. It is still possible to provide a custom type. (#1711)
12 -* Deploy - Architecture: We added the refresh button in the footer of the “Runtime details” popup in the Deploy Architecture. (#1708)
13 13  
14 -==== Bug fixes ====
8 +=====Minor changes=====
15 15  
16 -* Create - Flow designer: Resolved the issue where resizing columns in the ‘Java mail sender’ support object would make the columns ‘stick’ to the mouse. (#1320)
17 -* Create - Flow designer: Several broken Spring documentation references in help texts are updated to new documentation pages. (#1534)
18 -* Deploy - Releases: Changed the text on the wrench icon when hovering for the create phase release to “Property configuration“ to differentiate it from regular property releases. (#1571)
19 -* Deploy - Releases: Resolved the issue where resizing columns in the 'Compare properties' would prevent further interactions with the popup. (#1668)
20 -* Deploy - Releases: Warning message showing the set advised number of flows per container is fixed to show the correct number when a release is approved for the next environment. (#1059)
10 +* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
11 +* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
12 +* 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.
13 +* 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.
14 +* 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.
15 +* Deploy - Architecture: You can apply your changes to environment without having an active release.
16 +* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
17 +(control tower, so Gen3 only)
18 +* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
21 21  
20 +====Bug fixes====
22 22  
22 +* 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.
23 +* 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.
24 +
25 +====Remarks====
26 +
27 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.