frappe-impl-workflow

Frappe workflow implementation requires mapping intermediate approval states to doc_status 0, final states to doc_status 1, and cancelled states to doc_status 2 to prevent transition failures. This ensures valid state machine behavior across submittable and non-submittable DocTypes.

Frappe documents get stuck when workflow states lack valid transition rules or have overlapping conditions. Defining mutually exclusive transition conditions and mapping roles correctly prevents dead ends and ensures approval chains function properly.

Self-approval in Frappe workflows is blocked by configuring allow_self_approval settings within the workflow transition rules. This ensures users cannot approve documents they submitted, maintaining separation of duties in the approval chain.

Frappe workflows are tested programmatically using get_transitions and apply_workflow functions to validate every transition path. This testing approach verifies rejection loops, condition boundaries, and state changes across submittable DocTypes.

Conditional routing and email notifications are supported in Frappe workflows through transition rules with mutually exclusive conditions and automatic field updates on state change. This enables complex approval chains with rejection loops and send-back functionality.

Rejection and send-back loops in Frappe workflows are handled by defining transition rules that route documents back to previous states while maintaining proper doc_status alignment. Intermediate states use doc_status 0 to keep documents editable during the approval cycle.