Purchase Request Approval

Alpha notice: This walkthrough mirrors the hosted demo. Status names and thresholds are demo-specific.

What you will build

Draft / Rejected → Submit for internal review
    → Procurement Manager Review → Amount Gate
        → [amount >= 10000] Finance Review → Approved
        → [default] → Approved

After approval, host actions such as archive become available. ERP, PO creation, and payment logic stay outside DBFlow Core.

Business object

ProcurementRequest implements Workflowable and WorkflowContextInterface:

public function getWorkflowVariables(): array
{
    return [
        'amount' => (float) $this->amount,
        'department' => $this->department,
        // ...
    ];
}

Demo business status (ProcurementRequestStatus enum):

Demo source paths:

Workflow

Node keys:

• procurement_manager_review
• amount_gate
• finance_review (high amount only)
• end_approved

Amount condition: amount >= 10000 (ProcurementRequestWorkflow::CONDITION_HIGH_AMOUNT).

ProcurementRequestWorkflowSeeder builds the JSON graph, validates, and publishes — same pipeline as refund disputes.

Hooks keep DBFlow and host columns aligned:

Implementation: app/DBFlow/ProcurementRequest/ProcurementRequestWorkflowHooks.php.

Why this matters

• Clear draft → review → approved lifecycle on a familiar business object
• Amount-based escalation without ERP complexity
• Shows guarded downstream actions after approval
• Builds on the same patterns as Refund Approval

Minimal code

Submit for internal review is visible when status is draft or rejected, no running workflow exists, and the record is not archived.

DBFlow::start(
    ProcurementRequestWorkflow::KEY,
    $record,
    Auth::user(),
);

Assignees use My Tasks. Finance reviewers receive tasks only when amount >= 10000 routes through finance_review.

Guard post-approval business actions on host status — not workflow internals:

->visible(fn (ProcurementRequest $record): bool =>
    $record->status === ProcurementRequestStatus::Approved
)

DBFlow does not ship ERP adapters. If you sync to an external system, invoke that from WorkflowHooks::onApproved() or a host job — keep integration code in app/, not in Core.

Filament integration

ProcurementRequestResource composes HasLifecycleActions for submit, return-to-draft, and archive actions. ProcurementRequestWorkflowPresenter surfaces workflow metadata on the resource view.

Use Workflow Instances or the presenter link to inspect dbflow_workflow_logs through the Standard timeline. See Workflow Timeline.

What to try next

• Workflow Hooks → — onStarted / onApproved / onRejected / onCancelled reference
• Eloquent Models — traits and hooks overview
• Filament Resource Actions — action visibility patterns
• Refund Approval — simpler first example

Alpha caveats:

• Threshold (10000) and assignee user IDs are demo constants
• archived is a host-only state after approval — not an DBFlow end node
• Cancel hook rolls back to draft; adjust for your production policy
• Published definition must exist before DBFlow::start() — run Host Integration sync on deploy
• permission / callback assignees require registerAssigneeResolver() — not Laravel permission names