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

Next revision
Previous revision
tech2018:s2:poa_design [2018/06/04 20:14]
127.0.0.1 external edit
tech2018:s2:poa_design [2018/06/06 10:47] (current)
Gianluca Pelliccioli old revision restored (2018/06/06 12:36)
Line 1: Line 1:
  
  
-==== 1. Understand the process and roles (who is doing what) ==== 
- 
-The first thing you have to to is to mature the complete understanding of "who is doing what" to achieve your expected result.   
-If you are lucky enough this understanding should be based on a documented process that the business consultant should have shared.  
  
 ==== 2. Define the POA, forms fields and exit scenarios ==== ==== 2. Define the POA, forms fields and exit scenarios ====
Line 16: Line 12:
  
  
-==== 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. 
  
-==== 4. Define reporting/KPI on forms data ==== 
  
-Based on the process info we can suppose to have 2 KPI: 
-   * How many thrads landed in a quotation; 
-   * What is the date of sending of the quotation. 
  
  
-[[manual_process | Back to Manual Process]]+[[tech2018:s2:tech2018_engine | Back to: Workflow management]]
tech2018/s2/poa_design.1528143245.txt.gz ยท Last modified: 2018/06/06 10:36 (external edit)