StatusFlow is a module in WebProof that is normally used when a proof must be reviewed by a number of users (A g B g C) in a specific sequence, i.e. user A must review the proof before it can be reviewed by user B. However, all three users are still able to view the page.
When a status code is selected, it is no longer possible to add sticky notes to the page or to make further status code changes. A status flow can only be overruled if the user has been assigned a role that grants "Break Out" permission.
Note: Status flow is not available in FREE and BASIC WebProof versions. See more about FREE and BASIC setup here.
Creating a new Status Flow
- Right-click "Status Flows" under "Navigator/Settings" and select "New Status Flow".
- Enter the name of the status flow, including a description of what the flow does.
- Select the "Status Flow" tab, right-click the folder and select all of the status codes that will be used in this particular proofing process. Try to select them in chronological order.
- Complete with status codes.
- For each status code, select the next status code in the proofing process using the "Jump to" menu item.
- Complete status flow.
- The last status code has no "Jump to" option, which means that once it has been selected by a proofer, the page is CLOSED, allowing no further comments or status code changes (with the exception of users who have been assigned roles with the "Break Out" permission).
- The "Attach projects" tab is used to attach this status flow to the job(s) that will use it. Then click "OK".
- When this is done using a role that does not have the "Break Out" permission, the job is restricted to this fixed sequence, which can be quite complex if many users are involved.