Work Sample: Generic Approval Workflow using BRF+ Rule Engine

Example of a generic approval workflow based on rules in a BRF+ rule engine.   This rule engine completely separated all the business rules from the approval workflow.   Changes to the business rules can be easily configured without any changes being necessary to the workflow definition.  The workflow was designed for the vendor master but could easily be extended to other business objects.  

The configuration determine how many approval types are required based on rules that classify the object (in this case, the vendor master).   Based on the classification of the business object, approval types are defined.   Each business object may be assigned any where from zero to multiple apprlval types.

Each approval type has the following configured for it:

• Number of approval steps
• Sequential or parallel approval (parallel is much faster)
• Rules for finding the agent
• Rules for escalation (reminder to same agent or escalate approval to new agent)
• Is approval required or only notification (both are logged so it is clear who received approval or notification)

Attached below is a presentation that was used as a technical knowledge transfer.  It is quite technical but it does describe the workflow process.   It does show the level of transfer knowledge documentation that will be provided