Managing Work Orders23% of the exam
Service appointment parent records and work order hierarchy
How work orders, line items and service appointments fit together: which records can parent an appointment and why a work order or line item is recommended, what an appointment inherits from that parent, why a parent can't be changed, and how child work orders and Root Work Order build a hierarchy.
Given a scenario, recommend the appropriate relationship between Service Appointments, Work Orders, and Work Order Line Items.
~6 min read · 11 practice questions ·
What the exam expects
- Recommend one work order with several service appointments, line items with their own appointments, or separate or child work orders for a given job.
- Choose a valid service appointment parent and explain why a work order or line item parent is recommended (scheduling logic, mobile, optimization).
- Predict which appointment fields are inherited from a work order or line item parent, which are read only, and what stays blank for other parents.
- Fix an appointment created on the wrong parent, and report on a work order hierarchy.
Key terms:
- Service appointment: a visit to the customer with scheduling and assignment details.
- Parent Record: the record an appointment belongs to; it can't be updated after creation.
- Parent Record Status Category: read-only appointment field holding a work order or line item parent's status category.
- Child work order: a standalone work order whose Parent Work Order points to another work order.
- Root Work Order: read-only field holding the top-level work order of a hierarchy.
Key facts
Appointments per work order
- Detail
- Multiple, one per visit
Parent Record Type values
- Detail
- Account, Asset, Lead, Opportunity, Work Order, Work Order Line Item
Recommended parent
- Detail
- Work order or work order line item
Optimization scope
- Detail
- Only appointments with a work order or line item parent
Parent Record
- Detail
- Can't be updated after creation
Account on the appointment
- Detail
- Read only; inherited from a work order or line item parent, else blank
Work Type on the appointment
- Detail
- Read only, inherited from the parent
Duration on the appointment
- Detail
- Inherited, manually editable
Deleting a work order
- Detail
- Deletes its child appointments
Root Work Order
- Detail
- Read-only top-level work order of the hierarchy
Line item asset
- Detail
- Not inherited from the work order
Sources for this section (6)
- Create Service Appointmentshelp.salesforce.com (opens in a new tab)
- Appointment Fieldshelp.salesforce.com (opens in a new tab)
- Appointment Guidelineshelp.salesforce.com (opens in a new tab)
- Scheduled Jobshelp.salesforce.com (opens in a new tab)
- WorkOrderdeveloper.salesforce.com (opens in a new tab)
- WorkOrderLineItemdeveloper.salesforce.com (opens in a new tab)
- Why does an appointment created without scheduling distort capacity and utilization?
- When can a work order's Root Work Order equal its Parent Work Order?
- What happens to a work order's service appointments when the work order is deleted?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Agentforce Field Service and Operations Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 38 lessons of the Agentforce Field Service and Operations Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both