What must be enabled to use a task-driven lifecycle?

• A. Source Transformation
• B. Fix Scripts
• C. Enable state flows
• D. At least one WO Task

Answer: (C)

Task-driven lifecycles rely on a built-in mechanism that models how a task moves through different stages. This mechanism is provided by state flows. When state flows are enabled, the platform can drive the lifecycle of work orders and tasks using a defined graph of states and transitions, enforce valid moves between states, and present a clear progression trail. Without enabling this feature, the task-driven approach can’t operate because there’s no state-machine backbone to manage the lifecycle.

The other options don’t enable this capability: Source Transformation is about data mapping for integrations, not lifecycle management; Fix Scripts are for custom scripting and data fixes, not enabling lifecycle flows; having at least one Work Order Task is simply a resource and doesn’t activate the underlying mechanism that governs task transitions.