Changes for page 207 - Aligned State
Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 143.1
edited by Carlijn Kokkeler
on 2023/10/23 16:56
on 2023/10/23 16:56
Change comment:
There is no comment for this version
To version 144.1
edited by Carlijn Kokkeler
on 2023/10/23 16:59
on 2023/10/23 16:59
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -6,7 +6,8 @@ 6 6 7 7 * Design - Message Mapping: The button 'Import from Store' will directly open the store. 8 8 * Design - Performance: Performance improvements for the Flow Designer have been implemented. 9 -Create-Flowdesigner] When importing items from the store, flowfragments that are hidden in design will be listed under the versions in create. 9 +* Create - Flow Designer: When importing items from the store, flowfragments that are hidden in Design will be listed under the versions in Create. (#1044) 10 +* Create - Flow Designer: Resources without name won't trigger error messages when users select components. (#950) 10 10 * Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well. 11 11 * Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028) 12 12 * 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) ... ... @@ -20,10 +20,11 @@ 20 20 ====Bug fixes==== 21 21 22 22 * 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) 24 +* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused. 25 +* 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) 23 23 * Manage - Triggers: Besides checking error header, the error trigger is configured to check if an error message contains a term. 24 24 25 25 26 - 27 27 =====Infra and image changes===== 28 28 29 29 * 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.