Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 239.1
edited by Carlijn Kokkeler
on 2024/05/06 14:06
Change comment: There is no comment for this version
To version 140.1
edited by Carlijn Kokkeler
on 2023/10/23 16:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -220 - Patch Parade
1 +207 - Aligned State
Content
... ... @@ -1,14 +1,23 @@
1 -In the last sprint cycle, we have worked on a new runtime image LINK that contains a fix for an issue regarding SFTP sessions. Furthermore, we did several small improvements and many bug fixes.
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 did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.220 - Patch Parade||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State .WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 -Capture - Integrations: Information about the integration pattern of a selected message type has been added to the new integration pop-up. (#1214)
7 -Create - Flow designer: A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
8 -Deploy - Releases: Search boxes in the properties overview are now shown by default. (#1325)
9 -Manage - History: All events that relate to message queues (delete message, delete all messages or delete queue) are now logged in the Manage phase instead of the Deploy phase. (#1278)
5 +=====Minor changes=====
10 10  
7 +* 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.
8 +* Design - Message Mapping: The button 'Import from Store' will directly open the store.
9 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking.
10 +* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
11 +* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
11 11  
12 -=====Bug fixes=====
13 -Design - Message mapping: It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. (#1179)
14 -Create - Flow designer: It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. (#852)
13 +
14 +
15 +====Bug fixes====
16 +
17 +* 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.
18 +
19 +
20 +
21 +=====Infra and image changes=====
22 +
23 +* 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.