Skip to main content

Advanced practice: build and test an inspection workflow

A complete practice workflow using required fields, explicit branches, variables, and a final signature.

Written by Alex Merkin

This follow-on exercise assumes that you can create two steps, add a field, and connect a route. Its data and voltage limits are fictional training values. Use a practice draft and appropriate permissions; do not perform it on an active production workflow. Pause after each section and check the result before continuing.

After the first workflow exercise and the field/routing guides, build a six-step inspection workflow to practice the editor. The operator identifies a unit, inspects its appearance, measures voltage, and records PASS or HOLD before a final signed review.

Use a test environment. The 4.8–5.2 V limits below are fictional training data, not an engineering specification. HOLD is an inspection label in this exercise; it does not automatically freeze a Work Order or quarantine inventory.

1. Create the workflow

Create TRAINING — Bench inspection. In Workflow Settings, select an appropriate test Workflow Type and attach a test Part if that type requires one.

Create chapters Inspection, Disposition, and Closeout. Add these steps:

  1. Identify unit — Inspection.

  2. Visual inspection — Inspection.

  3. Measure output — Inspection.

  4. Accept unit — Disposition.

  5. Record hold — Disposition.

  6. Final review — Closeout.

Enable First Step only on Identify unit.

2. Write instructions and create fields

In Basic Info, write a short instruction for each step. Then add these Required fields in Enrichment:

  • Identify unit: Training unit reference, Input/Text, no default.

  • Visual inspection: Visual result, Radio or Select, options Pass and Fail, no preselected result.

  • Measure output: Output voltage (V), Input/Number, no default.

  • Record hold: Hold reason, Textarea, no default.

Explain the fictional 4.8–5.2 V acceptance range in Measure output's description. Do not restrict the input field to that range: the operator must be able to record a failed measurement.

3. Create the seven connections

Use Flow or the source step's Routing tab:

  • Identify unit → Visual inspection: no condition.

  • Visual inspection → Measure output: Visual result equals Pass.

  • Visual inspection → Record hold: Visual result equals Fail.

  • Measure output → Accept unit: voltage ≥ 4.8 AND voltage ≤ 5.2.

  • Measure output → Record hold: voltage < 4.8 OR voltage > 5.2.

  • Accept unit → Final review: no condition.

  • Record hold → Final review: no condition.

Final review has no outgoing route. Do not add a return loop or Show/Hide on the two branching source steps.

Both alternatives at each decision have explicit conditions. Remove any accidental extra connection that bypasses a check.

4. Record the outcome

In More → Variables, create Text variable inspectionOutcome, default Pending.

On Accept unit, add a trigger: Step Is Signed → Set Variable → inspectionOutcome → PASS.

On Record hold, add the corresponding trigger with value HOLD.

In Final review's description, use the rich-text variable picker to insert inspectionOutcome after “Inspection outcome:”. A plain typed variable name is not the inserted value.

Text variable inspectionOutcome with default Pending

In Manage Variables, inspectionOutcome has type Text and default Pending. Check these three values after creating the variable. The exercise’s triggers will later set the result to PASS or HOLD.

5. Add signature and time settings

On Final review, enable Electronic Signature. Keep one existing/default signing requirement for the base exercise. Do not add a second requirement simply to label the existing signer.

Choose step-level timing in Workflow Settings. Set Measure output's Standard Time to one minute for the timing test.

6. Save and test

Wait for Saved, reload, and confirm the configuration remains. Resolve validator errors and preview from the root.

Run these cases in fresh previews:

  • Pass with 5.0 V: Measure → Accept → Final review; result PASS.

  • Fail at Visual inspection: Hold → Final review; measurement skipped; result HOLD.

  • Pass with 4.7 V or 5.3 V: Measure → Hold → Final review; result HOLD.

  • Pass with exactly 4.8 V or 5.2 V: Accept path.

  • Missing unit reference, visual result, voltage, or hold reason: completion of that required-input step should be blocked.

  • More than one minute on Measure output: inspect the overrun display; time alone should not block completion.

For a validator exercise, temporarily clear First Step, inspect the missing-root error, then restore it. For an edit-recovery exercise, change a title, move focus outside the text field, and use Undo/Redo.

7. Verify a real test session

After the preview cases pass, publish in the test environment. Launch one PASS and one HOLD session through the intended test entry point.

Confirm the actual workflow version, fields, result display, electronic signature, and saved session record. Preview alone does not establish those results.

Record any discrepancy before adapting this exercise to a real process. For a later version-control exercise, change an instruction, inspect the draft/version behavior, compare versions, and test the next release separately.


Did this answer your question?