Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 148.1
edited by Carlijn Kokkeler
on 2023/10/24 12:33
Change comment: There is no comment for this version
To version 229.1
edited by Carlijn Kokkeler
on 2024/04/23 12:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +219 - Creation Carousel
Content
... ... @@ -1,33 +1,13 @@
1 -In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components and we did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
1 +In the last sprint cycle, we focused on releasing new [[environment templates>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for docker single and double lane. Moreover, we have worked on a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] that contains a fix regarding SFTP sessions. Furthermore, we developed a new version of our eMagiz Mendix connector to support Mendix version 10 and higher. Lastly, we did several bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State .WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.219 - Creation Carousel||target="blank"]].
4 4  
5 -=====Minor changes=====
5 +=====New features=====
6 6  
7 -* Design - Message Mapping: The button 'Import from Store' will directly open the store.
8 -* Create - Flow Designer: Performance improvements for the Flow Designer have been implemented.
9 -* Create - Flow Designer: When importing items from the store, flow fragments that are hidden in Design will be listed under the versions in Create. (#1044)
10 -* Create - Flow Designer: Resources without names won't trigger error messages when users select components. (#950)
11 -* Create - Flow Designer: We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
12 -* Create - Flow Designer: The performance of highlighting resources of selected components is improved in Read-only mode.
13 -* Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well.
14 -* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028)
15 -* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045)
16 -* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
17 -* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
18 -* Manage - Data Sink: The data sink page has been moved to the “Explore” tab. (#946)
19 -* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of the configured size used to 110%. The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
20 -* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
21 -* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
7 +*
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"]].
22 22  
23 -====Bug fixes====
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.
24 24  
25 -* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
26 -* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
27 -* Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087)
28 -* Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.
29 -
30 -
31 -=====Infra and image changes=====
32 -
33 -* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.