Which option indicates a Transfer Order Line Task exists to move lines across stages?

Which option indicates a Transfer Order Line Task exists to move lines across stages?

• A. Dispatcher Workspace
• B. Transfer Order Line Tasks
• C. Approval for new request required
• D. Task rejection reasons

Answer: (B)

Lines in a Transfer Order progress through their lifecycle using dedicated line-level tasks. Transfer Order Line Tasks represent the individual actions needed for each line item to move from one stage to the next, such as from created to in transit to completed. This per-line task structure lets you assign, track, and complete the exact step for every item independently, ensuring accurate progression across stages for the entire transfer. The other options point to UI or policy aspects rather than the mechanism for moving lines: a dispatcher's workspace is a dashboard for managing work, an approval requirement is a governance rule, and rejection reasons are outcomes tracked when tasks fail. None of these specifically denote the existence of a per-line task that enables moving lines across stages.

Lines in a Transfer Order progress through their lifecycle using dedicated line-level tasks. Transfer Order Line Tasks represent the individual actions needed for each line item to move from one stage to the next, such as from created to in transit to completed. This per-line task structure lets you assign, track, and complete the exact step for every item independently, ensuring accurate progression across stages for the entire transfer.

The other options point to UI or policy aspects rather than the mechanism for moving lines: a dispatcher's workspace is a dashboard for managing work, an approval requirement is a governance rule, and rejection reasons are outcomes tracked when tasks fail. None of these specifically denote the existence of a per-line task that enables moving lines across stages.