In WorkflowFirst, workflow is a lot like a "decision tree", with each branch being a choice of "stages" that's made by a user with a specific role. This lets you build complex workflow very quickly:
Let's keep going with some more options by adding substages to our workflow. Go back to the workflow designer, and click "Add Choice" under the stage we just added:
Each choice you add will create another option, or "decision", under the original stage. They will appear as buttons to the user. You will normally define different roles for each level, so it will be sent to that user to process.
In this example, we'll add an option for a manager to approve or reject the vacation request:
We'll start by adding the stage called "Approve":
Notice we can just enter in the name of the role - but if it's a role you've used before, you should be able to select it from the dropdown list (clicking "..." next to it).
For this one we'll add just one field - to let the manager enter in some coverage details (that is, information about who will be covering for the employee while they're away).
Now we'll click OK on that, and click the same "Add Choice" on the first stage to add a second option, applied to the same role, to let them reject the request.
This brings up the same stage editor, but we'll enter in Reject instead - and a field for the rejection reason. Because the Rejection Reason might be a few lines, we'll make the data type "Text (Paragraphs)".
Now we have something that looks more like a workflow chart!
We don't even have to finish there - perhaps after it's approved, it can be sent to Human Resources for processing.
Notice how the role name is displayed in the workflow chart, so you can easily see how it travels from one person to another.
Now publish and try it out!
Next Topic: Optional: Making Sub-Lists
Please post all questions on the support forum. Thank you.