Decision Flows
A decision flow is a named, versioned definition belonging to an account. Each decision flow accepts aan array of input records, evaluates them against your configured rules, and returns a per-record result containing a decision code, message, and any output fields the flow chose to emit.
Anatomy of a Decision Flow
| Concept | Description |
|---|---|
| Code | A short, human-readable identifier for the decision flow (e.g. AFFORD_V1) |
| Version | The published version to execute. Must be greater than zero. |
| Product Code | A billing code identifying the product being consumed. |
| Data | An array of input records; each record is a dictionary of string key/value pairs matching the flow's expected inputs |
How the Execution Works
- The source system collects the inputs required by the decision flow.
- It calls
POST /decisioning/v1/flows/executewith the flowcode,version,productCode, and adataarray of input records. - Decisioning loads the flow definition, evaluates the rules against each supplied record, and returns a per-record result.
- The source system inspects each record's
successandoutputfields to drive its next step (approve, decline, refer, request more data, etc.).
Accessing the API
- Contact us to enable Decisioning for your account
- Generate API credentials
- Authoring decision flows is done in the Principa Cloud Portal under Decision Studio
Continue: Decisioning API >>