How do I automatically route documents to the right team?
Use document metadata and FormKiQ rulesets to select the workflow that should handle a document. For example, document type and department can select a finance review workflow, whose steps assign work to the team's queues. First agree the business routing decisions, then configure their conditions, target workflows, evaluation triggers, and fallback behavior in FormKiQ.
Plan the routing decisions
Before configuring FormKiQ, agree which team should handle each document type and what information is needed to make that decision. Capture these requirements in your project notes, including how staff should handle missing or conflicting metadata.
For example: invoices identified as belonging to Finance should enter the finance review workflow; documents with an unknown department should go to an intake review workflow. This planning step gives administrators a clear set of requirements to implement.
Configure rulesets and workflows in FormKiQ
Create the target workflows and their team queues. Then configure ruleset rules with the document conditions and the target workflowId. For the Finance example, an ATTRIBUTE condition can match department with EQ and the value Finance. The workflow defines the review and queue steps after the rule matches.
Use the operations supported by the installed release. The documented rule schema lists EQ and CONTAINS; do not assume that it supports numeric greater-than or less-than conditions. If routing depends on an amount threshold, arrange a supported processing or integration step to set a routing attribute, then match that attribute in the ruleset.
Connect the ruleset to the supported processing or workflow entry point. Confirm whether evaluation runs on intake, after mapping, or on a later change. Metadata that becomes available only after OCR cannot choose an earlier route.
Verify boundaries and retries
Test each configured match, overlapping conditions, and documents with missing or unknown values. Confirm the intended workflow starts, the correct queue receives work, and only authorized members can read the document and act on it. If another processing step calculates a routing attribute, test that calculation separately, including threshold boundaries.
Handle duplicate evaluation and changes to already-routed documents. An intake event can be retried, and a later metadata correction may require review rather than silently repeating a completed approval. Record the result and provide an operational path for items that match no rule.
Edition and configuration
Rulesets, queues, and workflows are included from Essentials. OCR, mappings, or AI classification need their own configured processing path; the generative AI extension is separately selected for Advanced/Enterprise.