Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 264.1
edited by Danniar Firdausy
on 2023/11/08 16:19
Change comment: There is no comment for this version
To version 267.1
edited by Danniar Firdausy
on 2023/11/08 16:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -30,13 +30,13 @@
30 30  //__Consistent triggers naming__//
31 31  We noticed that Trigger types have a different name throughout the portal. Therefore, in this release, on the Manage - Alerting page, we have renamed the "Source" column to "Source trigger" so that we have a consistent naming.
32 32  
33 -//__Search phrase__//**
33 +//__Search phrase__//~*~*
34 34  We are now enabling users to search for log entries and error messages in the next-generation architecture models based on phrases containing two or more words, instead of only one word or the full sentence. This also means that the user can search for entries with distances of 2 or incomplete search phrases (e.g., “startin engine” to look for “starting servlet engine”).
35 35  
36 36  //__Improved image building performance__//
37 37  We have implemented an improvement on the preparation step of the release at the beginning of the deployment, which leads to a faster deployment process.
38 38  
39 -//__Default "errorChannel" on next-generation architecture migration__//**
39 +//__Default "errorChannel" on next-generation architecture migration__//~*~*
40 40  During a migration of a model to the next-generation architecture, we have introduced a check now for flows that did not have custom error handling to set their error channel to "errorChannel" after the migration if the custom error handling is set to false.
41 41  
42 42  == **Bug Fixes** ==
... ... @@ -44,7 +44,7 @@
44 44  //__Incorrect deployed containers__//
45 45  A fix has been implemented to address the issue where older containers were deployed while it was shown that the new ones were deployed. This problem was caused by auto-healing that was triggered during a new deployment.
46 46  
47 -//__Log messages in next-generation architecture models__//
47 +//__Log messages in next-generation architecture models__//~*~*
48 48  We have implemented an improvement in our infra components that is intended to reduce the occurrence of log messages failing to be sent in the next-generation architecture models.
49 49  
50 50  //__Random stuck in deployment plan execution__//
... ... @@ -74,8 +74,6 @@
74 74  Let's stay in touch and till next time!
75 75  
76 76  {{info}}
77 -~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78 -
79 79  ~*~* Indicates a next-generation-architecture only feature.
80 80  {{/info}})))((({{toc/}}))){{/container}}
81 81  {{/container}}