Differences

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

--- tech2018:s2:poa_design [2018/06/06 10:38]
Gianluca Pelliccioli
+++ tech2018:s2:poa_design [2018/06/06 10:47] (current)
Gianluca Pelliccioli old revision restored (2018/06/06 12:36)
@@ 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:
 ^ Activity type ^ Role ^ process ^ deliverables ^
-| VC_CALL | FO_SALES |
+| 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_QUOTATION | BO_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. |
@@ Line 22: / Line 16: @@
-[[manual_process | Back to Manual Process]]
+[[tech2018:s2:tech2018_engine | Back to: Workflow management]]