How do I build a document approval workflow?
Configure a FormKiQ workflow with queues and review or approval steps, then start it for the intended documents through an explicit action or supported ruleset. Assign authorized reviewers and define rejection and exception paths. A successful upload is not approval: inspect workflow state and decision history before allowing the next business operation.
Model the decision
Define what reviewers decide and which metadata must be complete first. An invoice review might confirm supplier identity and total before a finance approval step. Assign queues and authorized participants, and distinguish approval authority from permission to upload a document.
Configure the workflow using the walkthrough and validate its entry conditions. If a ruleset starts it, test which metadata change or processing event actually evaluates the rule. Prevent the same document from entering duplicate approval runs after retries.
Test the full outcome
Exercise approval, rejection, rework, a missing reviewer, processing failure, and an updated source document. Decide whether a changed revision needs a new decision. Inspect recorded workflow/step state and the current document revision before sending it to signing, payment, or publication.
For recurring business processes, use the corresponding packaged Business Solution when its application flow fits. Configure organization-specific queues, assignments, and rules within that solution rather than reproducing an entire business UI unnecessarily.
Edition and configuration
Workflows, queues, and rulesets are included in Essentials, Advanced, and Enterprise. They require configuration; they are not a separately purchased capability module. Selected signing or generation modules remain separate.