What is Workflow Testing?
Workflow Testing allows administrators to simulate the progression of a just-designed workflow by impersonating a member. This feature improves self-testing capabilities of enterprises for complex feature changes. It helps ensure workflows function correctly before deployment, preventing business disruptions caused by workflow errors while supporting quick troubleshooting and adjustments during the flow process.
This feature is particularly useful for complex, multi-departmental collaboration like procurement, inventory management, or sales pipelines.
What does It Look like?
Taking a Leave Application workflow as an example, an administrator can simulate the process as "Linda":
How to Test a Workflow?
Step 1 Entering the Setting Page
In Workflow, click the Test button in the upper right corner and select a member to simulate their identity. Then you can initiate the workflow test.
Step 2 Switching the Nodes
Click the Switch Node sidebar on the left to view the workflow diagram. Click any node in the diagram to view its specific progression effects.
Note:
You can only switch to upstream nodes that have already been tested.
Step 3 Restarting the Test
Here are two options for you.
Option 1 Restarting Completely
On the page of test progression, click Retest in the upper right corner to select a different member for simulation.
Option 2 Restarting Node-specifically
In Switch Node, click the button next to any node to restart testing from that specific one.
Note:
Restarting completely will clear all current test data, while restarting node-specifically preserves existing data.
Step 4 Viewing the Updates
Click the Updates sidebar on the right to view workflow history, notes, and other dynamic workflow information.
Note:
The "Process" function is not supported in the Updates during workflow testing.
Step 5 Testing Different Versions
Switch between different workflow versions to test the progression of each version.
More to Know
Please be aware of the following limitations during workflow testing:
Features like batch submit and overdue actions are not supported during workflow testing.
The start node cannot contain the fields of a related form.
In the start node, draft saving, duplicate value validation, and aggregate table validation are not supported.
If a node in the workflow involves the fields of a related form, add/import/export on the related form is not supported.
Member/department fields set to "Current User" or "Current User's Department" will display the actual logged-in user and department rather than the simulated initiator or node approver.
I have finished reading. 🏆
👉I can't wait to Try for Myself.
👉I need more HELP in Discord Forum.