Posted: 15 Mar 2019 6:19 EDT Last activity: 15 Mar 2019 11:39 EDT
Revalidate of rules to ensure they work properly
I have a question around revalidating specific rules after a major release. In our application we listed few set of rules that has to be revalidated in higher environments after every major release. Certain rules like Declare on Change, Declare Trigger, DB Table etc.,
We recently faced an issue after we performed a major release into pre prod Env. We performed revalidation for certain list of rules as we do always. But while Testing team has performed automation testing, there is an error that effected performance of a screen.
When we are debugging,it was identified that one section is having issue while refresh is done on change of a field .This section is having a field which has a when rule which is not loading properly after refresh of the section. The class and context of the section and when rule defined inside the section is same and should be picked in rule resolution hierarchy.
When we cannot find any issue around the rules, we did revalidate and save of that particular when rule as a last work around which unexpectedly resolved the issue.
This raised some queries around what type of rules should be considered for revalidation after any major release? Is it really the actual task that should be carried out which can resolve potential issues like this?
Ideally, It's not needed to revalidate rules after each prod release. Even I experienced the same in one of my project issues with declarative rules. I think to identify such rules early, better to check lower environments logs.