Table inheritance lets specialized records share fields and platform behavior with a parent. Parent-level rules can affect descendant records.
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 task-derived record inherits common task fields and potentially broad automation. 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: Inspect the hierarchy
A child table inherits shared parent fields and behavior.
Step 2: Review broad automation
A parent rule can affect several specialized record types.
Step 3: Test representative descendants
Narrow conditions should match intended table and operation scope.
Worked scenario
A task-derived record inherits common task fields and potentially broad automation.
A Task-level rule assumes every record follows an incident assignment policy. A request task also inherits Task behavior and may trigger it unexpectedly. Review hierarchy and conditions before treating the rule’s observed incident result as its complete impact.
Common mistake
A parent rule can have a wider impact than its author’s immediate example.
Verify the behavior
Exercise each relevant child type and confirm unrelated records are unchanged.
Interview exercise
Review an inherited rule.
Answer and reasoning
Inspect the table hierarchy, conditions and execution scope, then test representative child record types.
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.