====== Model handover by a sequence flow ====== {{tag>sequence_flow task event}} Model routine handover in course of a process by a sequence flow. ===== ✔ How to =====
Request to proposal
Request to proposal
Sales
Sales
Clarify client's needs
Clarify client's nee...
Send proposal
Send proposal
Engineering
Engineering
Create product specification
Create product speci...
Finance
Finance
Calculate price
Calculate price
===== ✘ How NOT to =====
Request to proposal
Request to proposal
Sales
Sales
Clarify client's needs
Clarify client's nee...
Pass request to Engineering
Pass request to Engi...
Engineering
Engineering
Accept request from Sales
Accept request from...
Create product specification
Create product speci...
Pass specification to Finance
Pass specification t...
Finance
Finance
Accept specification from Engineering
Accept specification...
Request to proposal
Request to proposal
Sales
Sales
Clarify client's needs
Clarify client's nee...
Send proposal
Send proposal
Engineering
Engineering
Create product specification
Create product speci...
Finance
Finance
Calculate price
Calculate price
===== Exceptions ===== * Sequence flow is sufficient when routine communcation means is used like interdepartment paper mail, email, ERP or workflow software. If a non-trivial communication is used (e.g. sending documents with courier) then it's OK to model it by a task. ===== See also ===== * [[en:rule:work_is_activity]] ===== Author(s) ===== --- //[[user:bell|Anatoly Belaychuk]] 2024-01-13 13:10//