CSA - Configuring Applications for Collaboration (20% of the exam) - Section 3

Advanced Form Configuration

Annotations, formatters, field dependencies and reference qualifiers, dictionary overrides, choice lists, mandatory and read-only settings, and where a form behaviour should be set (dictionary, UI policy, client script) so it applies consistently. Items ask which mechanism achieves a described form behaviour.

Dictionary entriesReference qualifiersForm annotations

Practice question for this objective

Free sampleConfiguring Applications for Collaborationhard

A custom table has a reference field pointing to the Configuration Item table. The field must offer only operational configuration items whose support group is a group the logged in user belongs to, and the restriction must apply both in the picker on the form and in the reference list every user opens, without any per user setup. Which mechanism meets this requirement?

AWrite an onChange client script on the reference field that reads the user's groups and clears the field whenever the chosen configuration item does not match.
BCreate a read access control rule on the Configuration Item table that grants access only when the record's support group is one of the current user's groups.
CDefine an advanced reference qualifier on the dictionary entry for the field that calls a script include returning an encoded query built from the current user's groups. Correct
DAdd a UI policy on the custom table whose condition inspects the support group of the selected item and makes the reference field read only when there is no match.

Filter which records a reference field offers by setting a reference qualifier on its dictionary entry, not by scripting on the form or restricting access. A reference qualifier lives on the field's dictionary entry and is appended to the query the platform runs whenever it resolves that reference, so it constrains the picker, the reference list and any lookup consistently for every user. An advanced qualifier calling a script include lets the query be built from the current user's group membership at run time, which a static condition cannot do.

Why A is wrong: Tempting because it does react to the user's own group membership, but it runs only after a value is chosen on a form, leaves the full list visible in the picker and does nothing for records set by server side code.

Why B is wrong: Tempting because it would narrow what the picker returns, but it also hides those configuration items everywhere else on the instance, which is a far wider change than filtering one reference field.

Why C is correct: Correct, because the reference qualifier is stored on the field's dictionary entry and is applied server side to every query behind the picker and the reference list, so all users get the filtered set with no per user configuration.

Why D is wrong: Tempting because UI policies are the no code answer for many form behaviours, but a UI policy governs field state rather than which records a reference field offers, so the unwanted items stay selectable.

See more CSA practice questions, answers explained.

Exam traps in Configuring Applications for Collaboration

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.

Write an onChange client script on Category that removes the choices that do not belong to the selected value, then restores the full set whenever Category is cleared again.
Why it is wrong: Tempting because the script does produce the filtered list a user sees, but it hand codes behaviour the dictionary supports directly and has to be maintained again every time a new subcategory value is added.
Change the field's choice specification to a dropdown that omits the empty entry, so users are pushed to type into the control when no configured value is suitable.
Why it is wrong: Tempting because removing the empty entry is a genuine choice specification setting, but it only controls whether a blank value is offered and still restricts the user to the configured values.
A read access control rule on the new field denies access, so the field must be granted to the roles those users hold.
Why it is wrong: Tempting because a field level read denial does remove a field from the form, but such a denial would also strip the column from the list, and the users can already read it there.

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