As discussed earlier, a workflow consists of a series of ordered steps that a case must go through to become work that is quality-checked, approved, and publish-ready. You can think of a step in a workflow simply as a level in a computer game. For every level, you can perform necessary actions. When you satisfy one level’s set of conditions, you advance to a higher level.
When you design the workflow steps, one thing to consider is how to group the stages each case has to go through (e.g., sending an estimate, approving a pending case, etc.) and conditions (PM or customer’s requirements) into steps. The results in one step are processed to conclusion before going on to the next step. You may want to group in the same actions so that each result will follow logically from the previous one.
When you design your workflow, it is important to understand how the workflow treats each step. In the following table, things like how a step affects the workflow and how each steps work are discussed:
- Go to Settings > System Settings > Workflow Settings.
- Select the Workflow Structure that you want to implement in your system. As you click on a radio button, the names of the workflow steps become editable.
- In the Quality workflow additional options, select the account that you want to use as the Default system quality assurance account. If you can recall, there’s a Send to QA button when a case is In Progress state. When a user clicks on the button, the case gets automatically assigned to the default QA account.
Note: You can also assign a Default system quality assurance account per project. You can control this in Settings > Accounts Settings > Projects.
