Business Process Management
Communication can be a document, a dialog, a sticker on the document, a data record, an e-mail or a voice mail and all of it is business process driven. The Papyrus process engine does not use a simplistic procedural flowchart graph to define the process but instead the Papyrus BPM is State and Event driven to avoid problems associated with parallel activities and the rigid sequence of a procedure. This state and event driven process does not require complex decision blocks nor listen-for-event-loops. All changes of the process are defined in the Desktop and stored in the central WebRepository.
Benefits/Gains to be achieved |
• |
There is less process tuning and correction because an unforeseeable event sequence does not invalidate the process |
• |
If you change the state engine and event definition of one item all processes using this item will automatically be updated |
• |
Changes of the process do not require Java coding |
• |
No programming of dialogs required |
|
