Workflow - Cascading Signatures
Database Monitor allows you to set up a process whereby users are notified in sequence depending upon the level they are at within the workflow. For example, if we want Melissa to be the last person to sign off on a change that was initiated by Carl and subsequently reviewed by Amanda, we might have them set in the workflow as:
|
Carl |
Level 1 |
|
Amanda |
Level 2 |
|
Melissa |
Level 9 |
Rules for using levels
General Rules:
- Level 0 users activate as soon as the workflow is activated.
- Level 0 users may sign off at any time and do not affect subsequent levels' notifications or signature activations.
- There may be several users at any given level; however, users at higher numbered levels will receive notification only after all signatures are posted by all users at all lower levels
- There MUST be at least one user at level 0 OR level 1.
- Workflows with multiple levels must start with a level 1.
- Level numbers do not have to be assigned in sequential fashion. For example, you can establish a sequence such as- 1, 2, 3, or 1, 3,9. Either of these would be valid. Levels of 2, 3, and 4, however, would be invalid as all workflows with levels 2 or above must have a level 1.
Levels Defined
|
Level |
Function |
|---|---|
|
0 |
Level 0 is used if all notifications are sent at the same time to all recipients. Note: a workflow must have at least one level 0 or level 1 user |
|
1 |
Level 1 is used if notifications are to be sent in a sequential manner. Note: a workflow must have at least one level 0 or level 1 user |
|
2..9 |
Level 2 through level 9 will receive notification only after all users at all lower levels have signed. |