CSA - Data Migration and Integration (13% of the exam) - Section 6

UI Policies

UI policies and UI policy actions that make fields mandatory, read-only or visible on the client when conditions are met, ordering and the reverse-if-false option, catalog UI policies, and when a UI policy is the right tool compared with a client script or a data policy.

UI policiesData policies

Practice question for this objective

Free sampleData Migration and Integrationmedium

An administrator must make the Caller field read only on the Incident form whenever State is Closed. No calculation, no message to the user and no server side enforcement is required. Which choice is the appropriate tool, and for what reason?

AAn onLoad client script, because a script is required to read the State value while the form is rendering and set the Caller field accordingly.
BA before business rule that sets the Caller field to read only, because server side logic controls how fields behave when the record is presented.
CA UI policy with a read only action on the Caller field and a condition of State is Closed, because it satisfies the requirement without any code. Correct
DAn access control rule granting write on the Caller field to holders of the itil role, because access control governs when a field may be edited.

A UI policy is the preferred no-code tool for setting fields mandatory, read only or visible on a form when a stated condition is met. UI policies apply mandatory, read only and visible actions on the client whenever their condition matches, and they re-evaluate as the user edits the form, so no code is needed for a straightforward state rule. Client scripts are reserved for behaviour a UI policy cannot express, such as calculations, messages or field values derived from other records. Business rules and access control rules operate on data and on security respectively.

Why A is wrong: Tempting because an onLoad script can set a field read only, but it would only act at load time and it writes code for behaviour the platform configures declaratively.

Why B is wrong: Tempting because before rules run on save and can alter a record, but business rules act on data rather than on the appearance of fields in the browser.

Why C is correct: Correct because a UI policy is the declarative tool for mandatory, read only and visible field state, and it re-evaluates as the State value changes on the form.

Why D is wrong: Tempting because a write rule does make a field uneditable for some users, but it keys on role and record conditions for security rather than on form state for usability.

See more CSA practice questions, answers explained.

Exam traps in Data Migration and Integration

Answers that look right on this material and are not. Each one is a distractor from a different question in the CSA bank for this domain.

A UI policy on the Requested Item table with a visible action on the Return Date field, since the variable values are stored against that record.
Why it is wrong: Tempting because the ordered item does carry the variable values, but a table UI policy targets dictionary fields on the form and does not act on the variables presented on the ordering screen.
A client script on the Requested Item table that hides the Return Date field whenever Loaner Required holds any value other than Yes when the item is ordered.
Why it is wrong: Tempting because a client script can control field visibility, but a script scoped to the Requested Item table does not run while a user is completing the item in the catalog, and it adds code where a declarative rule exists.
A data policy, because it governs field behaviour on the form alone and is configured without any script being written
Why it is wrong: Tempting because a data policy is configured without script, but it enforces mandatory and read only rules on the data itself, including imports and web services, not on form behaviour alone.

Examworthy is not affiliated with or endorsed by ServiceNow. Original, blueprint-aligned practice material only.