When customers call in for support at AW Computing, a case is always created.

a separate Work Order Entitlement Process is the appropriate Field Service design. Entitlement Processes are object-specific. A Case process does not automatically govern a Work Order merely because the Work Order originated from the Case. The Work Order needs an applicable entitlement process of Work Order type so milestones can be instantiated and displayed.

Reusable configuration should be preferred over duplicating records or custom objects. Work Types can standardize duration, required skills, required products, and Knowledge, while the Work Order hierarchy and Work Order Line Item hierarchy are available when genuinely separate but related work must be represented.

The alternatives address different parts of the Field Service model. Adding the Lightning component alone does not create milestone instances, and sharing the Case entitlement does not make a Case process execute against Work Orders.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Work Order Entitlements; Entitlement Processes; Milestones.