Designing interfaces and user experiences →mediumMultiple ChoiceObjective-mapped

SNOW-CAD Designing interfaces and user experiences Practice Question

A form has a field 'Department' that, when changed, should make 'Manager' mandatory. The current implementation uses a client script that updates the field attribute on change. However, the mandatory behavior only works when the user first loads the form, but not when changing the field. What is the most likely cause?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

A UI Policy with same condition is overriding the client script.

The script should use a UI Policy instead, as client scripts for such actions require proper event bindings and are less reliable.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
A UI Policy with same condition is overriding the client script.
Why this is correct
UI Policies run after client scripts and can overwrite the mandatory setting.
✗
The client script is not triggered because the field change event is not handled.
Why it's wrong here
Client scripts can handle onChange, but the issue is that the mandatory attribute is not persisted.
✗
The script uses g_form.setMandatory() which only works on initial load, not on change.
Why it's wrong here
setMandatory works on change as well, but it may be overwritten by a UI Policy.
✗
The field is referenced by the wrong name.
Why it's wrong here
If the name were wrong, it wouldn't work at all.

Go deeper

SNOW-CAD Designing interfaces and user experiences Practice Question

Why each option matters

Option-by-option breakdown

Related to this question