Purchase Request Approval
Routes a purchase request through a delegation-of-authority matrix kept in DMN, so finance can change who approves what without touching the process. Small requests are approved automatically; the rest go to the approver group the table names, and an approved request becomes a purchase order in the ERP.
Scenarios · 3
- A request under 500 is approved without review route-request → auto-approve → create-po → po-created
- An IT purchase is routed to IT managers and approved route-request → approve-request → create-po → po-created
- A large request the CFO office rejects approve-request → notify-rejected → request-rejected
Job types · 2
-
erp-purchase-order-createCreate purchase order -
requester-notifyNotify requester: rejected, Notify requester: approved
Files · 3
- purchase-request-approval.bpmn Process model
- purchase-request-approval.bpmn.tests.json Test scenarios (runScenario format)
- approval-matrix.dmn DMN decision
Every scenario passes on @bpmnkit/engine's runScenario in the
package's tests. casen template use purchase-request-approval [dir] writes the files above
into your project — see the templates guide for running
the scenarios and deploying.