Correspondence

Question 1

Main parts and approach of notification

Answer 1

Who - Work Parties
How - e-mail, text message, fax, mail
When - start of an assignment, missed deadline, change of status

Approach:

1. Ask questions to establish need (trigger, channel, intent)
2. Identify best approach (shapes, flow action)
3. Document the need appropriately:
   - Assignment: with the assignment spec
   - Flow action: with the flow action spec
   - Smart Shape/Utility: correspondence spec

Question 2

Work parties (who)

Answer 2

“Originator” – the person who created the case.

“Manager” to model the person who might be responsible for approvals and oversight.

“Customer” can refer to a person on whose behalf the case is transacted. (a “customer” may sometimes be the “originator” of a case, but not always)

“Interested” to model someone who needs to be aware of the case progress, but is not personally involved in processing that case.

• “work party” allows us to create a placeholder – a page on the clipboard - with information collected from the case.
• avoids the need to hard-code user details, some of which we can’t possibly know until after the case is created.

Question 3

Default workparty

Answer 3

pyCaseManagementDefault:

• Customer (Subject)
• Owner
• Interested

Question 4

when

Answer 4

atomated:

• sent automatically when a shape is reached
• Shapes: Send Email, Assignment, Utility

manual:

• local action (connector)
• at the operator discretion

Question 5

Options to send from an assignment

Answer 5

• Nofify
• NotifyAll
• NotifyAllAssigned
• NotifyAssignee
• NotifyParty