Question 390
A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field. Before changing the configuration, which evidence should the administrator examine FIRST?
Explanation
Correct Answer
Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. A UI Policy can behave differently on initial load and later changes; ignoring reverse conditions often leaves stale field states. The appropriate response is: Configure whether conditional UI Policy behavior applies when a form loads and whether actions reverse when its condition becomes false; verify all transition paths. Scenario: A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field.
Incorrect Answers
Inspect entry paths (form, API, import), condition semantics, data policy/ACL coverage, and records written without the browser UI. This evidence is relevant to UI Policy versus server-side data enforcement, not the most diagnostic first check for this failure. Examine: Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. Scenario: A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field.
Inspect affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts. This evidence is relevant to UI Policy actions for conditional field behavior, not the most diagnostic first check for this failure. Examine: Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. Scenario: A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field.
Review available themes, portal branding configuration, workspace branding support, accessible color contrast, change scope and instance policies. This evidence is relevant to Instance branding and portal experience settings, not the most diagnostic first check for this failure. Examine: Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. Scenario: A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field.


