Changes for page 220 - Patch Parade
Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 148.1
edited by Carlijn Kokkeler
on 2023/10/24 12:33
on 2023/10/24 12:33
Change comment:
There is no comment for this version
To version 239.1
edited by Carlijn Kokkeler
on 2024/05/06 14:06
on 2024/05/06 14:06
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -20 7-Aligned State1 +220 - Patch Parade - Content
-
... ... @@ -1,33 +1,14 @@ 1 -In the last sprint cycle, we focused ondelivering state generationcomponents.Ontopofthat,we madeseveralimprovements regardingthealignmentof componentsandwe did someperformanceimprovements and bug fixes.Moreover, we made a change in the metrics storage duration.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. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.20 7-Aligned State.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.220 - Patch Parade||target="blank"]]. 4 4 5 -=====Minor changes===== 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) 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) 22 22 23 -====Bug fixes==== 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. 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)