Testing a workflow
The Test tab runs the saved draft on emails you choose. Nothing is sent or created in MCS, and nobody is asked to approve. Documents are read and MCS is looked up for real, so you see real results.
Running a test
- Open the workflow and go to Test.
- Choose up to 10 emails from the 30 most recent your company received.
- Select Run test.
The test uses the draft, or the live version if there is no draft.
What you see
For each email, every step with its result. Steps that would act are marked "Not done in a test", with what they would have done:
| Step | Shows |
|---|---|
| Reply | "Would reply:" and the text |
| Create in MCS | "Would create ... in MCS", with Show what would be sent, or what is missing |
| Ask the sender | "Would ask the sender about 2 things" |
| A person approves | "Would wait for a person" and why, or "No person needed here" |
| File in MCS | Which MCS custom field it would attach to |
| Choice | "Took the If side" or "Took the Otherwise side" |
A test never makes a contact and never splits a batch.
Good habits
- Test with a mix of emails: easy ones, ones with missing details, and awkward ones.
- After changing a check or a field description, test again on the emails that caused trouble.
- After publishing, use the dashboard's Why items needed a person chart to see which steps to improve next.
- To rerun a real work item on the live version, use Start again on the work item.