Build an approval workflow
Create phases, configure review steps, add conditions, and test your approval routing.
Table of Contents
Who this is for: administrators configuring form workflows.
Use this guide to turn an approval policy into phases, review steps, and conditions. For the underlying concepts, start with Understand approval phases, steps, and routing.
1. Plan the workflow before configuring it
A phase determines when reviews happen. A step defines an individual review within a phase. Put reviews in separate phases when one must finish before the next begins; put steps in the same phase when they can run in parallel.
This worked example uses a conflict-of-interest form with three Yes/No questions: an overall conflict question, an employee-relationship question, and an outside-employment question. Replace these with the questions and reviewers required by your policy.
| Phase | Step and destination | When it runs |
|---|---|---|
| 1 | Manager — submitter’s direct manager | Overall conflict answer is Yes |
| 2 | Compliance — Compliance review group | Overall conflict answer is Yes |
| 2, alongside Compliance | HR — HR review group | Employee relationship is Yes OR outside employment is Yes |
| 3 | Additional review — your designated specialist group | Outside employment is Yes |
Manager review comes first. Compliance and HR can then review together. The additional review follows the required Phase 2 approvals only when its condition matches. The screenshots show the controls in a documentation form; its existing Manager, Compliance, and HR steps are arranged sequentially. Follow the phase placement in the table to build the parallel example.
2. Open the form and check prerequisites
- Switch to admin view and open Form builder.
- Select the form you want to configure, then select Workflow.
- Check the current phase numbers, step names, and routing summaries before adding anything. If a suitable step already exists, use its Configure control instead of creating a duplicate.
- Confirm that the questions used in your conditions exist and that their answer options are correct.
- Prepare the destination groups and verify their eligible members. For manager routing, verify the submitter’s manager relationship and decide who takes over if no manager can be found.
See Configure approver groups and routing tables for destination setup. Build and test policy changes in your test environment before applying them to your production form.

3. Configure the first Manager step
- Find the first phase, labeled Starts at submission. Open Configure on its Manager step. If you are starting with an empty workflow, add its initial approval step, then use the same settings below.
- Set Name to Manager. This is the step name shown on the record.
- Under Who approves at this step, select Submitter’s manager.
- Set Level to Level 1 (direct manager) for this example.
- Set Decides to The request. This example makes a decision on the whole request.
- Add the condition overall conflict question → is equal to → A value → Yes, following section 6 below.
- Under If this step’s approver cannot be found, choose the fallback required by your policy. For example, choose Approver group and select your Compliance group.
- Review the remaining settings described in section 7. Select Save step when editing an existing step, or Add step when creating one.
Use a positive Yes condition for this example. The screenshot illustrates an existing configuration using “when none of these are true” with No. That is a different condition expression; do not copy it without considering unanswered or unavailable values.

4. Create the next phase with a Compliance step
- Return to the workflow canvas.
- To append a phase after the last phase, select Add the next phase. To insert one between existing phases, select Add a phase here at that position.
- The Add approval step panel opens. You create the phase by configuring its first step; there is no separate phase-name field in this panel.
- Enter Compliance in Name.
- Select Approver group under Who approves at this step, then select your Compliance group.
- Review the group’s displayed decision rule. Leave Approvals required empty to follow that rule, or enter the required number only when your policy calls for a step-specific approval count.
- Keep Decides set to The request. Add the overall conflict equals Yes condition.
- Complete the fallback and update settings, then select Add step.
- Check that Compliance appears in Phase 2, after Manager. If you inserted a phase, recheck the numbering and order of the phases below it.

5. Add a parallel HR step and a later conditional phase
- Within Phase 2, select Add a step that runs alongside. Use the control inside the Compliance phase, not the control after it.
- Name the step HR. Select Approver group and your HR group.
- Set its conditions to run when either the employee-relationship answer or the outside-employment answer is Yes, as detailed below.
- Complete the other settings and select Add step.
- Confirm that Compliance and HR share the same phase number. Putting HR in its own later phase makes it sequential instead.
- To add the final conditional review, select Add the next phase after Phase 2. Name its first step Additional review, choose the designated group, and add outside-employment question is equal to Yes.
- Select Add step and confirm that this step is in Phase 3.
Adding multiple people to one approver group does not create multiple steps. Use separate steps when the reviews need separate destinations, conditions, or settings.
6. Add and combine conditions
Conditions answer “Does this step apply to this submission?” They do not choose the approver; the destination is configured separately.
- In the step panel, find When does it run?
- Choose the matching mode. For the HR example, select when any of these are true.
- Select Add a condition.
- In When, select the employee-relationship question.
- In Condition, select is equal to.
- Set Compare with to A value, then set Value to Yes.
- Select Add a condition again. Choose the outside-employment question, is equal to, A value, and Yes.
- Read both rows and the matching mode together before saving. The HR step should run when either answer is Yes.

| Matching mode | Meaning | Example |
|---|---|---|
| when all of these are true | Every condition must match (AND). | Outside employment is Yes AND employee relationship is Yes. |
| when any of these are true | At least one condition must match (OR). | Outside employment is Yes OR employee relationship is Yes. |
| when none of these are true | No listed condition may match. | Neither listed answer equals Yes. |
| No conditions | The editor states that an empty condition list runs on every record. | A mandatory review that is not conditional. |
Add alternatives creates a nested condition group with its own matching mode. Use it when a rule needs grouping, such as A AND (B OR C): choose “all” for the outer group, add A there, then add an alternatives group set to “any” containing B and C. Do not leave an empty alternatives group; complete it or remove it before saving.
Available operators and value controls depend on the selected field. Test blank values, hidden questions, and boundary values relevant to your rule. “Not No” and “Yes” should not be assumed equivalent when an answer can be missing.
7. Check decision, escalation, and update settings
| Setting | What to check |
|---|---|
| Who approves at this step | Select the destination, such as a specific person, approver group, or submitter’s manager. Complete the additional fields for that destination. |
| Group decision rule / Approvals required | The group’s displayed rule determines how its members decide. For example, Anyone allows a single member’s decision to resolve the group. The optional approval count controls how many group members must approve; leaving it empty follows the group’s rule. |
| Decides | Choose the scope of the decision. This guide uses The request. Recipient-benefit decisions are a different scope and need their own policy and testing. |
| If this step’s approver cannot be found | Choose a fallback or Wait for an approver. Without a fallback, the step waits; it does not become an unmatched submission. |
| Stage type | Approval supports an approval decision. A Review stage asks the reviewer to mark the record reviewed and offers no reject action. |
| When the record is updated | Review whether existing decisions should be kept or updated entries reviewed again. The editor notes that this applies to entries the submitter updated. Test the behavior your policy requires. |
| Clear some entries without review | This is a separate control for clearing entries without review. Leave it off for this whole-request example; do not enable it as a substitute for a missing reviewer. |
8. Define what happens when no step matches
- Find Unmatched submissions below the workflow.
- For this example, leave Auto-approve submissions that match no step off.
- Set Send to to Approver group, then select the Compliance group.
- If your policy explicitly permits automatic approval for unmatched submissions, configure that instead and test the no-match case.
- Review What it reads. These are the questions the workflow depends on; changing or removing them can change the approval path.
Two different situations: no step matches → the unmatched-submission settings apply. A step matches but its reviewer cannot be found → that step’s fallback or waiting behavior applies.

9. Save, test, and publish
- Select Add step or Save step in each step panel. Check the workflow summary and wait for the form’s Saved indicator.
- Check every phase number, step destination, matching mode, condition value, and fallback. Saving a configuration and publishing a form are separate actions.
- In your test environment, select the form’s Publish control when ready. Resolve any validation issues and complete the confirmation shown. Verify the published version before testing submissions against it.
- Submit representative test requests and inspect their Review timeline. Complete the applicable review actions and check when later phases become available.
- Use the test matrix below. After correcting a configuration, publish the corrected test version and rerun affected cases.
- Apply and publish the validated configuration in production according to your organization’s change process.
| Test | Expected result for the worked example |
|---|---|
| Overall conflict Yes; employee relationship No; outside employment No | Manager, then Compliance. HR and Additional review do not apply. |
| Overall conflict Yes; employee relationship Yes; outside employment No | Manager, then Compliance and HR in the same phase. No Additional review. |
| Overall conflict Yes; outside employment Yes | Manager, then Compliance and HR together, then Additional review. |
| No configured step matches | The configured unmatched destination receives the request; it must not auto-approve in this example. |
| Manager is unavailable | The Manager step follows its configured fallback. It must not use the unmatched path merely because a reviewer is missing. |
| Destination group has no eligible member | The step follows its fallback or waits. Check the timeline message. |
| One of two parallel reviews is complete | The next phase must not start while another required review in the current phase is still outstanding. |
| Relevant answers change | Verify the configured update behavior and resulting timeline. |
For reading the result, see Review a disclosure and follow its approval progress. Record the reference, published form version, answers, expected path, and actual timeline for each test.
10. Troubleshoot an unexpected route
- A step runs too often: check for an empty condition list, an “any” mode used instead of “all,” or a condition that also matches missing values.
- A step never runs: check the selected question, operator, value, and whether the question is answered on that submission.
- Reviews happen in the wrong order: compare phase numbers. “Runs alongside” creates a parallel step; a new phase creates a later stage.
- The request is waiting: check the current timeline, reviewer eligibility, and step-level fallback before changing unmatched-submission behavior.
- Saved changes are not reflected in a new test: verify the published version and test with a new submission. Do not assume a saved draft is the version being used.