Changes for page 262 - Good News
Last modified by Erik Bakker on 2026/02/23 08:06
From version 299.1
edited by Erik Bakker
on 2025/12/01 09:38
on 2025/12/01 09:38
Change comment:
There is no comment for this version
To version 82.1
edited by Erik Bakker
on 2023/05/22 15:19
on 2023/05/22 15:19
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 - 258 -ValeBene1 +198 - Great Migration - Content
-
... ... @@ -1,17 +1,27 @@ 1 - This release featuresvarious updatestoour platform,just beforetheholidayseason.Thiswillbe ourlastreleaseoftheyear.Wewillbebackreleasing more on **January15th**.Withthisrelease,you canenjoyanimproveduser experienceinspecific sectionsoftheplatform.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.258 -ValeBene.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 -* Deploy - Architecture: The memory limit for specific failover containers for on-premises Windows machines can be altered by our support department if necessary. 8 8 9 -==== Bugfixes====8 +=====Minor changes===== 10 10 11 -* Design - Data Model (Message Format): Viewing and editing permissions for the message format of different message types are fixed. The checks are corrected for all message types. (#1050) 12 -* Create - Add Integrations: Assigning a target namespace to messages based on the system being identified as a "SOAP entry connector" is corrected. Event processors no longer get the target namespace. (#1183) 13 -* Create - System Message / Data Model Message: The UI is updated immediately after removing restrictions for an attribute without the need to refresh the page. (#1707) 14 -* Create - Add Resource (Multiple places): Fixed a bug where when uploading a new (flow) resource in Create, one could select the eMagiz-generated “message definition” & “message transformation”. These, along with two deprecated resource file types, have been removed from the selectable types. 15 -* Create - Help Texts: We have fixed a bug in our help texts where the text would not show for specific input fields. 16 -* Manage - Queue dashboard: Updated message throughput panel to sometimes filter out spikey first and last observations. (#1589) 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. 17 17 20 +====Bug fixes==== 21 + 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.