An administrator must ensure that the Justification field is populated whenever a request record is saved, including when records arrive through an import set or an inbound web service call rather than through a form. Which mechanism enforces the rule in all of those cases?
- AA UI policy on the table with a mandatory action on the Justification field, applied to every view of the form.
- BAn onSubmit client script that cancels the save when the Justification field is empty, so no record can be written without it.
- CA data policy on the table with the Justification field marked mandatory, since data policies are evaluated on the server for any insert or update. Correct
- DA UI policy with the Reverse if false option cleared, so the mandatory action persists once the condition has matched.
Why A is wrong: Tempting because a UI policy is the standard no-code way to make a field mandatory, but its actions run only in the browser on a loaded form, so an import or a web service insert bypasses it entirely.
Why B is wrong: Tempting because an onSubmit script does block a form save, but like a UI policy it is client side code that never executes for an import set row or a web service insert.
Why C is correct: Correct because a data policy runs server side, so the mandatory rule holds for form saves, import set loads and web service calls alike.
Why D is wrong: Tempting because clearing Reverse if false does make an action persist, but it only changes what happens when the condition stops matching on the form and adds no server side enforcement.