Workflow Checklist

This does not apply if using a “Request Submitted” or “Job Completed” trigger to start the workflow and you creating your conditions based on the trigger.

If you are testing a request or job status, or a value from the request or job forms, you need to have a Request Status Change (Accepted/Rejected) or a Job Status Change (Completed/Cancelled) connector before the Exclusive Branch Connector.

Even if you are testing a user-entered value, you must have the status change connector or the workflow will go straight to the branching and not wait for the user to fill in the form. The test will then work on the default values of the form and the same branch will be taken over and over again and the other branches missed.

The status change connector does not need to be immediately above the branching - it could be further back up the flow. But it must occur before the branching.

Checking for submitted is only valid you had an already accepted/rejected request, and then someone manually makes it submitted again.

When you create a Request in a workflow, the Request is created in Submitted status. There isn’t a Draft status on the server like there is on the Mobile. So don’t create a Request and then immediately check the Submitted status as it will always be true.

If you have only one then the workflow will never go beyond this point in the workflow and the workflow will never be complete. This will active workflows in the workflow history, long after they should have finished.

If you have only one then the workflow will never go beyond this point in the workflow and the workflow will never be complete. This will active workflows in the workflow history, long after they should have finished.