Status flags are an aspect of tasks in a workflow that can be useful to group tasks, and are often used to indicate tasks that need a higher priority or extra attention. For example, status flags can be used to signal tasks that have been returned to a previous state, tasks that are considered critical or time-sensitive, tasks that have errors, etc.
When a status flag is applied, it is specific to the task-in-state, similar to an assignee. An assignee does not travel with an object throughout the workflow, rather it is assigned at entry to each state, and upon exit from any state the current assignee is not retained (unless business rules are set up to record this information). Furthermore, when an object exits a workflow, there is no longer any assignee associated with it.
Status flags should be thought of in the same way as assignees. Configuring status flags requires the understanding that they are specific to a task in a state, and therefore must be applied at entry to any state. In addition, tasks in parallel states of a workflow may have different status flags applied in each state.
This section of the documentation describes how to configure status flags.
First, a place must be created to store the status flags, which is described in the Initial Setup for Status Flags topic
Second, status flags must be configured for the particular workflow(s) in which they should be used, which is described in the Configuring Status Flags topic here.