Approval workflows are everyday actions that businesses perform on a routine basis. This tutorial will show how easy it is to create an Approval Workflow using . We will start with a simple workflow and add to it for each example discussed to demonstrate some design patterns and different features. The final workflow will be an example of a services Purchase Order workflow. We will create:
- A screenflow - allows you to collect a lot of information in a series of small steps
- A workflow where one of the steps is performed by someone outside the company (anonymous)
- An Approval workflow where one of the steps is only routed for additional approvals if certain conditions are met.
If you need basic help using the Flow designer, please refer to the Getting Started with FlowsWorkflows guide, and then return here.
What are we going to build?
Many companies offer software services to their new and existing clients. The final workflow in this tutorial will be a Purchase Order workflow for services that follows this business scenario:
- A sales person accesses the company's Purchase Order form, fills in the customer's email address and other required information, signs it and clicks Continue.
- sends a customized email to the customer that contains a link to the PO.
- The customer clicks on the link, reviews the Purchase Order, approves and signs it or sends it back to the company for corrections
- The workflow is routed back to the sales person.
- The sales person reviews the PO, and sends it to his manager for approval. The manager receives an email.
- The manager clicks on the link in the notification email, logs onto to review the PO via the Task List. He approves or sends it back to the sales person for corrections.
- If approved by the manager and the total amount of the PO is greater than $10,000.00, the workflow is routed to the VP for final approval.