Skip to Content

Changes for page 217 - Template Tango

Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 1.1
edited by eMagiz
on 2022/10/14 13:36
Change comment: There is no comment for this version
To version 59.1
edited by Erik Bakker
on 2023/03/14 08:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - Get Ready
1 +194 - Giant Leap
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -1,18 +1,33 @@
1 -Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.184 - New Beginnings.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.194 - Giant Leap.WebHome||target= "blank"]].
4 4  
5 5  =====New features=====
6 -* Create - new flow designer has been introduced for all users in the Create phase
7 - ** Right hand panel that displays alerts, properties, support objects and resources
8 - ** Objects can now be put on the canvas without a full configuration
9 - ** Alerts are generated to display incorrect or incomplete configuration
10 - ** Flow versions can be pushed to Deploy only when there are no remaining alerts
11 11  
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)
12 12  
13 13  =====Minor changes=====
14 -* Deploy - Copy property page changed to have a orientation on the runtime. Includes update to that popup for the field runtime
15 15  
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.
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 graph and made some small visual improvements.
17 +* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833)
16 16  
17 17  ====Bug fixes====
18 -* Feedback widget - introduced new version and fixed the interaction
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.
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)
29 +* Manage - Alerting: Editable column shows the correct value.
30 +
31 +====Remarks====
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.