Acceptance scenarios before releasing a workflow

Write the expected outcome Record inputs, acting role and expected outcome before running each scenario. “The workflow works” is not testable; “an incomplete request returns to its submitter” is.

Test with different roles An administrator account does not reveal every access problem. Submitters, specialists and approvers should only see permitted tasks and information. Include external users where relevant.

Exercise returns and rejection Which fields can change after a return? Does earlier decision history remain? What does rejection mean for the remaining work? Resolve these questions before handover.

Retain the scenarios Keep scenarios and outcomes with the process version so they can be reused after changes. Read about deployment and training, sign in to BPMS or discuss acceptance scope.