Service management deep-dive · LessonBy Neelima, ServiceNow Architect · Published · ServiceNow · all levels
Assignment and routing
Route work with assignment rules, data lookup rules, and when to move logic into a flow.
Quick answer
Route work with assignment rules, data lookup rules, and when to move logic into a flow.
Key takeaways
- Assignment rules run in order, first match wins
- Data lookup handles value setting without script
- Move complex routing to a flow rather than nesting conditions
- Review routing regularly, it drifts with the org chart
Three routing tools
Assignment rules set assignment group and assigned to from conditions. Data lookup rules set field values, typically priority from impact and urgency, using a lookup table instead of script. Flows handle routing that depends on external data or multi step logic.
Order and conflicts
Assignment rules run in order and the first match wins. Keep the list short and give each rule a clear condition, because a long unordered list is impossible to debug when a ticket lands in the wrong queue.
Maintainability
Routing changes often, so make it data driven.
- Prefer a lookup table over ten rules with hard coded values
- Document why each rule exists in the description field
- Review routing quarterly with the service desk, dead rules accumulate
- Log unmatched cases so gaps surface instead of defaulting silently
Practice challenge
+0 XPStreak ×0
Question 1 of 2
Which tool sets priority from impact and urgency?
Frequently asked questions
Assignment rule or business rule?
Use an assignment rule when the condition is simple data matching. Business rules for routing become invisible logic that new admins never find.
Why did priority not change when I edited the matrix?
Priority usually comes from a data lookup rule. Editing the field default has no effect while the lookup runs after it.