Question 620
A ServiceNow administrator finds: Two active UI policies alternately mark a request field both mandatory and optional under overlapping conditions. The intended correction must preserve access controls, business process consistency and the supported platform configuration. Which administrative change most directly addresses this specific failure?
Explanation
Correct Answer
The decisive detail is: Two active UI policies alternately mark a request field both mandatory and optional under overlapping conditions. The appropriate control is: Review UI policy execution, reverse-if-false behavior and competing conditions across the target forms and experiences. It addresses the risk that conflicting client-side policies can produce inconsistent required fields and prevent valid submissions for some user experiences. Check effectiveness with: Conflict tests evaluate both true and false conditions and compare supported desktop or workspace behavior against the intended specification.
Incorrect Answers
Ui policies conditional field behavior: A client-side UI policy is not a substitute for server-side data validation or ACLs and may fail to protect API updates. That mechanism alone cannot establish Ui policy order and cross-experience compatibility for this question.
Update set promotion dependency and rollback tracking: Out-of-order promotion or lost source identities can create untraceable production differences and make rollback unsafe. Here the decisive check is Ui policy order and cross-experience compatibility, not that separate capability.
Business rule recursion conditions and safe scripting: Unconditional current.update calls and broad triggers can repeat operations or overload the instance while masking the original change. The observed issue still requires Ui policy order and cross-experience compatibility; the proposed alternative tests another control.