A visual rules engine that determines which templates are triggered based on incoming payload data. Business users configure it in the workbench. Developers integrate it once. When conditions change, no deployment is required.
When document selection logic lives in application code, every regulatory change becomes an engineering task. A new state added to a product, a new document required for a loan type, a form that only applies above a certain transaction value: each one requires a code change, a review cycle, and a deployment for something that has nothing to do with your application's core function.
The rules engine moves that logic into the workbench. Business users define which templates fire under which conditions. Developers integrate the API once. When the conditions change, compliance updates the workbench. Engineering is not involved.
The rules engine is a configuration layer that sits between the approval workbench and the generation API. Templates must be approved in the workbench before they are eligible to be selected by a rule. The API evaluates the rules at generation time and serves only approved versions. Changing a rule does not require a deployment. Adding a new template to a rule requires only that the template has completed its approval workflow.
We will walk through the rules engine with your document selection logic in mind.