CRM B2C, customer (person) management

The difference from previous use case group is :

1. person form is more simple than in HR
2. role will be used to characterize customer position (suspect, prospect, with_Quote, customer)

Menu option to manage employee

• find (with role field), list, show, add, edit and manage his
  • contact informations
  • identification (3 idTypes, one mandatory, two optionals)
• template page with a header (or sidebar or ...) to show on which customer we are

Use Case Screen :

1. find Person with an add button (which can be show or not depending on parameter or authorization)
   • search field same as in HR find person
   • role field which can appear or not, when not appear a fix value has been put as parameters.
   • contact information field, phone, mail, town. These fields can be show or not by the user with a "deploy" button
2. Person list with an add button (which can be show or not depending on parameter or authorization)
   • role field appear or not, when not appear a fix value has been put as parameters, so only person with this role appear
3. add a Person, all main informations in the form
   • role
   • less field about person than in HR form
   • 1 postal address
   • 2 phone number
   • 1 identification number
4. show a Person, all main informations in the screen with indicator for contact information and identification when there are more data that what it's show.
5. show a Person with sub-menu with options :
   • contact informations
   • Identifications
   • role history
   • change role : a direct action button
6. edit a Person, only "Person" field
7. a button bar to change role (ex: for a suspect, there are the 3 options), this use case is for having a action bar, in this business process case it's maybe not a need, but for more complex object like order or task, it's a classical need.
8. List of all contact informations for a person, with one or multiple add buttons (which can be show or not depending on parameter or authorization) and purpose are show, it's the second step, with purpose management.
9. add a postal address (or just a purpose)
10. add a mail
11. add a phone number
12. edit a postal address
13. edit a mail
14. edit a phone number
15. List of all identification number for a person, with an add button (which can be show or not depending on parameter or authorization)
16. add a identification number with choice of identification type
17. edit a identification number with choice of identification type

Use Case Page :

1. create a new entry in CRM (role is choose during creation)
2. search a "customer" (or suspect, prospect, ...)
3. visualize a "customer"
4. manage informations about a "customer"
5. template page with a header (or sidebar or ...) to show on which "customer" we are, (for example to show all his quotes, or his orders, or ...)
6. manage informations about a person on one page, and with access at this page directly by a field (auto-completion on id, first, last name)