User Tools

Site Tools


tech2018:s2:poa_design

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
tech2018:s2:poa_design [2018/06/06 10:44]
Gianluca Pelliccioli old revision restored (2018/06/06 12:36)
tech2018:s2:poa_design [2018/06/06 10:46]
Gianluca Pelliccioli [3. Define companies and routings]
Line 1: Line 1:
  
 +==== 3. Define companies and routings ====
 +
 +The scenario is pretty straight-forward:
 +   * We have 2 roles: FO_SALES and BO_SALES
 +   * We have 2 companies, FO_COMPANY and BO_COMPANY.
 +
 +When the first activity is created it must be assigned to the company FO_SALES.
 +When the second activity is created it must be assigned to the company BO_SALES.
  
  
-==== 2. Define the POA, forms fields and exit scenarios ==== 
  
 Based on the simple process we have, this is the list of activities we assume to have: Based on the simple process we have, this is the list of activities we assume to have:
  
 ^ Activity type ^ Role ^ process ^ deliverables ^ ^ Activity type ^ Role ^ process ^ deliverables ^
-| VC_CALL | FO_SALES | The user will call the prospect and ask if there is any interest on the product Vacuum Cleaner. If YES then he/she will create a new activity for back-office in order to create and send a customized quotation. Otherwise the operator will just close the thread | The RESULT variable will tell if the process should proceed or not +| VC_CALL | FO_SALES |  
-| VC_QUOTATION | BO_SALES| The backoffice operator will create and deliver a customized quotation  for the Vacuum Cleaner  | The DATE of sending can be a reasonable info to be stored. | +| VC_QUOTATION | BO_SALES|  
  
  
Line 15: Line 23:
  
  
-[[manual_process | Back to Manual Process]]+[[tech2018:s2:tech2018_engine | Back to: Workflow management]]
tech2018/s2/poa_design.txt · Last modified: 2018/06/06 10:47 by Gianluca Pelliccioli