Flows coordinate triggers and actions through explicit workflow state. Keep trigger conditions and duplicate handling clear.
Before you start
You should understand tables, records and the difference between client-side and server-side scripts. Work in a development instance with representative permissions. Identify execution scope, transaction timing and the current user before attributing behavior to a platform script or business rule.
The practical goal is to reason through this situation: A request approval flow starts only for the intended state transition. Read the walkthrough first, then try the interview exercise before opening its answer. The important part is explaining the decision and its consequences, rather than remembering a definition alone.
Step-by-step walkthrough
Step 1: Define one trigger
The intended state transition should start one logical workflow.
Step 2: Assign side effects
Avoid a flow and business rule both performing the same action.
Step 3: Encapsulate complex logic
Use focused supported actions or server helpers where declarative logic becomes opaque.
Worked scenario
A request approval flow starts only for the intended state transition.
A request update starts a flow that sends approval email, while a legacy rule sends it too. Both work individually yet produce duplicates together. Inventory automation ownership and make the transition condition explicit; workflow tooling does not remove the need for idempotency and clear responsibility.
Common mistake
Overlapping flows and business rules can perform the same side effect twice.
Verify the behavior
Repeat updates and inspect flow executions plus resulting side effects.
Interview exercise
Choose flow versus script.
Answer and reasoning
Use declarative workflow where it stays clear, and encapsulate complex reusable logic behind controlled actions or server helpers.
Continue learning
Compare the scenario with the ServiceNow interview questions and test your understanding with the ServiceNow MCQs. For terminology and implementation details, consult the reference material.