Task Assignment and Transfer

  • January 31, 2013
  • Scott
  • 0 Comments

Anatoly’s 2nd BPMN Assumption is that the organization has mechanisms for task assignment and transfer.  This is, strangely, one of the things that trips up people new to BPM.  Why?  Because in traditional flowcharts, the hand-off is something you would likely model or draw.

And, because often they don’t know how the BPMS works, so they don’t know that these hand-offs are handled transparently by the platform itself, typically requiring no code at all.

But the final reason is that it is simply the right abstraction and simplification of the model to not explicitly model these deadweight items.  In the diagram below, crossing swimlanes and starting a new activity implicitly transfers control to a new group (Accounting), and initiates a new task for a member of that group.

Credit: Anatoly's

It is also surprising to me how much code goes into handling these assignments and transfers in traditional software platforms that are not BPM or Workflow friendly.

 

Related Posts
  • October 10, 2017
  • Ariana
  • 0 Comments

Planning Your Project Roadmap from BP3 on Vimeo. In this video, Andrew Paier talks through getting started ...

  • October 5, 2017
  • Scott
  • 0 Comments

Great article by Olan Anesini on the subject of process + data science over on Medium.  It's a theme we've be...

  • September 26, 2017
  • Ariana
  • 1 Comments

How BP3 Helps Customers with Digital Transformation from BP3 on Vimeo. Chief Strategy Officer, Amit Malhotr...