Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 60.1
edited by Erik Bakker
on 2023/03/14 08:53
Change comment: There is no comment for this version
To version 83.1
edited by Erik Bakker
on 2023/05/22 15:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -194 - Giant Leap
1 +198 - Great Migration
Content
... ... @@ -1,33 +1,24 @@
1 -The release introduces improvements to our 3rd generation runtime architecture and other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements.
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.194 - Giant Leap.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 -
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 -
10 10  =====Minor changes=====
11 11  
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 use custom error handling on your event processors.
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 chart, and made minor visual improvements.
17 -* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833)
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: You can apply your changes to environment without having an active release.
13 +* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
14 +(control tower, so Gen3 only)
15 +* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
18 18  
19 19  ====Bug fixes====
20 20  
21 -* Generic: We fixed an issue in 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 the resource selection popup of a 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 filenames (>100 characters).
25 -* Deploy - Releases: You need edit rights in the test environment of the deploy phase to execute the “Update flows to latest versions” action.
26 -* Manage - Dashboard: We update the view to visualize the split entries after you migrate 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 it occurred (#825)
28 -* Manage - Logging: Reduced the occurrence of 'Failed to send to Elastic' log messages which trigger alerts. (#898)
29 -* Manage - Alerting: Editable column shows the correct value.
19 +* 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.
20 +* 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.
30 30  
31 31  ====Remarks====
32 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 incompatible with the selected feature until the migration is finished.
24 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.