Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10

From version 250.5
edited by Danniar Firdausy
on 2023/11/07 08:45
Change comment: There is no comment for this version
To version 250.1
edited by Danniar Firdausy
on 2023/11/06 16:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -19,24 +19,11 @@
19 19  //__Improved Information on Removing a Release Version__//
20 20  Users are now informed with a more comprehensive information of why removing a release version that is still active on all environments (i.e., Test, Acceptance, and Production) is failed. Users are now informed in which environment(s) that runs in which runtime(s) that the release version under deletion is still running.
21 21  
22 -//__Wider and Expandable Fields for XPath Expressions__//
22 +//Wider and Expandable Fields for XPath Expressions__//
23 23  Input fields for XPath expressions located in the Create phase are now made wider and also capable of expanding when the expression registered by the user is too long.
24 24  
25 -//__Old Images Cleanup Mechanism__//
26 -We implemented a functionality that removes related unused images upon removal of a release version for on-premises machines. This prevents eMagiz to take resources of the customer’s machine due to the unattended old images.
27 27  
28 -//__Consistent Toggle Switches__//
29 -We are now implementing eMagiz Design System module in our platform and, in this release, we have updated all instances of the toggle switch to have a more consistent performance and look & feel throughout the platform.
30 -
31 -//__Search Phrase__//
32 -We are now enabling users to search for log entries and error messages based on phrases containing two or more words, instead of only one word or the full sentence. This also means that user can search for entries with distances of 2 or incomplete search phrase (e.g., “startin engine” to look for “starting servlet engine”).
33 33  
34 -//__Improved Image Building Performance__//
35 -We have implemented an improvement on the preparing step of the release at the begining of the deployment, which leads to a faster deployment process.
36 -
37 -//__Default "errorChannel" on Gen3 Migration__//
38 -There are cases where flows uring Gen3 Migration of a model.
39 -
40 40  == **Bug Fixes** ==
41 41  
42 42  //__Topic and event-processor names__//