PrimeForce / Modules / Workflow

Workflow

One engine serves leave, gratuity, payroll approval and settlement — because the document reference is deliberately soft, so the engine never has to know what it is approving.

What it does

A generic approval engine the other modules delegate to. Define steps, participants, triggers and applicability once; any document type that opts in routes through it. People action their queue from My Tasks.

  • Definitions you author, not hard-coded chains
  • Escalation on a timer, every 15 minutes
  • Delegation with automatic expiry
  • Full transition and step-evaluation logs
  • Standalone tasks with progress milestones
Screens in this module
· Workflow Dashboard
· My Tasks
· Definitions
· Applicability
· Instances
· Delegations
· Standalone Tasks
Capabilities

What that means in practice.

Definitions, then instances

A definition is the template — steps, participants, triggers, applicability. An instance is one running copy against one document. They are separate concepts and the product keeps them separate.

Escalation every fifteen minutes

A background job sweeps for overdue steps across every company on a quarter-hour cadence. Escalation is not something an administrator triggers.

Delegation that expires itself

Delegations carry a date range and a daily job expires them, so cover for annual leave does not silently become permanent.

A decision trail per instance

Transition log, step-evaluation log, participant log and task comments. Why a step routed the way it did is recoverable, not inferred.

Standalone tasks

Work that is not a document approval — with progress milestones and a verification step of its own.

Next

See it against your own numbers.

Bring a payroll period you have already closed. We configure the components, run it, and show you the variance against your figures.