Skip to Content

Changes for page 219 - Creation Carousel

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 62.1
edited by Erik Bakker
on 2023/04/11 08:29
Change comment: There is no comment for this version
To version 225.1
edited by Carlijn Kokkeler
on 2024/04/23 12:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -195 - Easter Party
1 +219 - Creation Carousel
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,34 +1,13 @@
1 -As a quarter has come to a close we went silent for a couple of weeks to plan ahead for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with good spirit after solving several smaller feedback items and bugs reported by you. In this and the upcoming release several of those stories will be included. On top of that we introduce various improvements to our API Gateway pattern and to our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the various improvements.
1 +In the last sprint cycle, we focused on releasing a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. Please refer to our new [[runtime image>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]] and Spring 6 [[migration path>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]] for more information. Apart from this, we have improved event streaming logging, such that these logs are not cluttered with irrelevant information anymore. Moreover, we have removed the deprecated cloud option 'Root' from the portal.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.195 - Easter Party.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.218 - Sprightly Spring||target="blank"]].
4 4  
5 5  =====New features=====
6 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)
7 +* Architecture: Several components are affected by the migration to Spring 6. Please check out our [[release blog>>Main.Release Information.Release Blogs.218 - Sprightly Spring||target="blank"]] for specifications.
8 +* Architecture: Moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]].
9 9  
10 10  =====Minor changes=====
11 +* Manage - Monitoring: Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs.
12 +* Deploy - Cloud: Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
11 11  
12 -* Design - Architecture: New calculation for topic size is applied and the feedback on topic retentions bytes has more information.
13 -* 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.
14 -* Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807)
15 -* Deploy - User Management: Roles are sorted alphabetically. (#806)
16 -* 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.
17 -* 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.
18 -* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833)
19 -
20 -====Bug fixes====
21 -
22 -* Generic: We fixed an issue in that you may see a screen with a broken styling when switching among phases.
23 -* Create - Flow Designer: Removed the option to create a new resource on the resource selection popup of a simple XSD schema support object.
24 -* 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)
25 -* Create - Resources: We fixed an issue when deploying flows with uploaded resources with very long filenames (>100 characters).
26 -* Deploy - Releases: You need edit rights in the test environment of the deploy phase to execute the “Update flows to latest versions” action.
27 -* Manage - Dashboard: We update the view to visualize the split entries after you migrate combined entries.
28 -* 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)
29 -* Manage - Logging: Reduced the occurrence of 'Failed to send to Elastic' log messages which trigger alerts. (#898)
30 -* Manage - Alerting: Editable column shows the correct value.
31 -
32 -====Remarks====
33 -
34 -* 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.