Tom à Calvin

Calvin à Mike

Mike à Dave

Dave à Ryan

Ryan à Clerks (Shaun)

Shaun is Clerk (and can move ahead the workflow to the next step at any time)

Scenario One – Straight up to each person

1. Tom Submits Document (Type: Workflow, Security Group: Public)

2. Calvin gets email requesting approval while Mike is now also on the approval list (but doesn’t get notified).

3. Calvin approves the document and Mike gets an email requesting approval while Dave is now also on the approval list (but doesn’t get notified).

4. Mike approves the document and Dave gets an email requesting approval while Ryan is now also on the approval list (but doesn’t get notified).

5. Dave approves the document and Ryan gets an email requesting approval.

6. Ryan approves and it gets sent to Clerks

Scenario Two – Skipping a Manager

1. Tom Submits Document

2. Calvin gets email but is away and cannot approve.

3. Mike is also on the approval list and is able to check his workflow and approve the document and Dave should get an email requesting approval.

4. Dave gets an email but is away and cannot approve.

5. Ryan is also on the approval list and is able to check his workflow and approve the document and Clerks should get an email requesting approval.

Scenario Three – Rejecting a Document

1. Tom Submits Document

2. Calvin gets an email and rejects the document.

3. Tom should get an email requesting that he fix something and checks in a revision to the original document and Calvin should get notified to approve the document again and he does.

4. Mike gets an email but is away so Dave looks and rejects the document.

5. Tom should get an email requesting that he fix something and checks in a revision to the original document and Dave should get notified to approve the document and he does. (May get sent to Mike again).

Scenario Four – Clerk moving things along

1. Tom Submits Document

2. Calvin gets email but is not available and it is due to the CAO today.

3. Clerks checks their workflow and approve the document (Note: may be able to update the metadata to Route_To CAO).

4. Approving the document should move it one step so Mike should get an email requesting approval but Clerks approves again.

5. Email sent to Dave for approval but Clerks approves again.

6. Email sent to Ryan for approval but Clerks approves again.

7. Clerks should get an email for approval.

Scenario Five – Route_To option (only used for Upper Management)

1. Tom Submits Document but knows that Calvin and Mike are away so he changes the Route_To to Dave.

2. Dave approves the document.

3. Ryan gets an email and rejects document.

4. Tom should get an email requesting that he fix something and checks in a revision to the original document and Ryan should get notified to approve the document again and he does.

5. Ryan approves.

6. Clerks should get an email for approval.