Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I've found more useful and rewarding to introduce BPM in companies that already have some formal business process established already- </p> <p>Application workflows are more in the line to automate user interaction only ( documents, authorizations, signatures etc. ) . But when it comes to user/systems interaction, BPM comes very handy.</p> <p>It is not only the final user can see and understand the real flow of the app ( for they won't move a finger to make any changes that's fine ) But to avoid repeating task, or complex interaction between systems. </p> <p>Of course you may code this in an app starting from 0 but it does not makes sense or scale when a Business process may actually be used for other process as a service. BPM suites let you do this in a couple of hours ( actually couple of click but don't tell the customer ) </p> <p>So going back to your question and depending on the BPM tool capacities, if there is already a business process and that process requires interaction among users of <strong>different</strong> ( this is important ) areas and different systems it is worth to introduce the BPM.</p> <p>If the interaction is more "human oriented" ( documents, approvals, etc ) App Workflow will do ( or BPM used as workflow if they already have the tool ) </p> <p>If the interaction is amog users of the same area, or the data is relatively easy to consume and nobody cares about the Business Process ( ie. who's turn to go for sodas ) , you can create a web/desk app from scratch. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload