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

Business Rules

Server-side business rules: when they run (before, after, async, display), the table, conditions and actions, setting field values without script, order of execution, and how business rules differ from client scripts and flows. Items pick the rule type and timing for a described requirement.

Business rules

Practice question for this objective

Free sampleData Migration and Integrationhard

Two before business rules run on the change request table, both carrying an order value of 100. One derives a Risk value from a lookup, the other reads Risk to set the Assignment group. The second rule sometimes finds Risk empty and leaves the Assignment group blank. The Assignment group must be stored by the same write that saves the record. What corrects the behaviour?

AGive the rule that derives Risk a lower order value than the rule that reads it, so the derivation runs first. Correct
BChange the rule that reads Risk into an after business rule so that it runs once the record has been written.
CChange the rule that derives Risk into a display business rule so that the value is set before the form is submitted.
DMove the assignment group logic into an onChange client script on the Risk field so that it runs on the form.

Sequence business rules that share a timing by setting ascending order values, because rules with equal order have no guaranteed execution sequence. Order of execution within a timing slot is governed by the order value, with lower numbers running first. When two rules carry the same order the platform gives no guarantee about which runs first, so a rule that depends on a value another rule produces must be given the higher order value, keeping both inside the single before phase and therefore the single database write.

Why A is correct: Correct because rules sharing a timing run in ascending order value, so lowering the derivation rule's order guarantees Risk is populated in memory before the second rule reads it in the same write.

Why B is wrong: Tempting because the Risk value would certainly be set by then, but an after rule would need a second write to store the Assignment group, which the requirement rules out.

Why C is wrong: Tempting because a display rule does run earlier than a before rule, but it runs at form load and would not fire for a record saved by an import or an integration.

Why D is wrong: Tempting because it reacts the moment Risk changes, but a server side before rule setting Risk does not fire an onChange event, and the script would not run outside the form at all.

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.

Order is evaluated across every table on the instance, so a rule on the incident table is sequenced against rules that run on the change request table as well as its own.
Why it is wrong: Tempting because the order value is a plain number with no table in it, but sequencing applies to the rules running on the record being written, not across unrelated tables.
The Advanced section of the rule, which exposes a field and value pair for assignment once the timing has been chosen on the When to run tab.
Why it is wrong: The Advanced setting is genuinely where extra rule configuration appears, so it is a reasonable guess, but what it reveals is the script field rather than a no-code field assignment.
An after business rule on the incident table that writes the configuration value into a spare field on the incident record.
Why it is wrong: Tempting because the client script could then read a field, but the after rule runs on save, so the value is only present on the next form load and the table carries data it does not own.

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