A task dependency can override the task ordering rules when:

A task dependency can override the task ordering rules when:

• A. Time interval for maintenance
• B. Enable the work.management.use.mandatory.skills property
• C. Final status when customer is presented an order summary
• D. Assignment method to use when approval is required

Answer: (D)

Task dependencies set a rule that one task must wait for another to finish, and in FSM those rules can take precedence over the normal task sequence when approvals are involved. The way work is assigned when approval is required can change the flow, allowing the dependency to control the order of tasks by routing and allocating work in a way that respects the prerequisite and the required approval step. So, the dependency can override standard ordering specifically through the assignment method used for approval-required work. The other options don’t impact how dependencies alter task order: scheduling time windows, mandatory-skill constraints, or the final status shown to the customer don’t govern the sequencing dictated by dependencies in an approval context.

Task dependencies set a rule that one task must wait for another to finish, and in FSM those rules can take precedence over the normal task sequence when approvals are involved. The way work is assigned when approval is required can change the flow, allowing the dependency to control the order of tasks by routing and allocating work in a way that respects the prerequisite and the required approval step. So, the dependency can override standard ordering specifically through the assignment method used for approval-required work. The other options don’t impact how dependencies alter task order: scheduling time windows, mandatory-skill constraints, or the final status shown to the customer don’t govern the sequencing dictated by dependencies in an approval context.