Skip to Content

Changes for page 194 - Giant Leap

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

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
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.
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.
2 2  
3 3  Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.194 - Giant Leap.WebHome||target= "blank"]].
4 4  
... ... @@ -5,29 +5,29 @@
5 5  =====New features=====
6 6  
7 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)
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 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 are using custom error handling on your event processors or not.
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 13  * Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807)
14 14  * Deploy - User Management: Roles are sorted alphabetically. (#806)
15 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.
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 17  * Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833)
18 18  
19 19  ====Bug fixes====
20 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.
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 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)
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 29  * Manage - Alerting: Editable column shows the correct value.
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 not compatible with the selected feature until migration has finished.
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.