Workflows
A workflow is a configurable sequence of steps that processes an evaluation — collecting data, calling enrichments, applying rules, and returning a decision.
A workflow is a configurable sequence of steps that automates decision-making in RiskOS™. When an evaluation is triggered, RiskOS™ executes the specified workflow — processing data through input collection, enrichment calls, conditional logic, and rules — to reach a final decision.
You build workflows visually in the RiskOS™ Dashboard using the Workflow Editor.
What a workflow does
A workflow defines:
- What data to accept — The Input step specifies required fields in the evaluation payload.
- What data services to call — Enrichment steps call Socure products or third-party APIs for additional signals.
- How to evaluate the data — Condition steps, Rule Scorecards, and Transformation steps apply logic to route and score data.
- What decision to return — A Decision step or Manual Review step terminates the workflow with an outcome.
Custom workflows vs Hosted Flows
RiskOS™ supports two workflow delivery models. Both use the same evaluation runtime, enrichment pipeline, and decision model.
| Aspect | Custom workflow | Hosted Flow |
|---|---|---|
| Configuration | Built and managed by the customer in the Workflow Editor | Preconfigured with a Socure-managed end-user UI |
| End-user UI | Customer-built (API + SDK) | Socure-hosted (web-based) |
| Extensibility | Full — any step type, any enrichment, any rule | Template customization and branding |
Both models produce evaluations, return decisions, and follow the same lifecycle states. The distinction is operational — ownership and configuration model — not architectural.
Related topics
- Workflow Steps Reference — Step-level configuration and field definitions
- Manage Workflow Lifecycle — Draft → Published → Live
- Hosted Flows — The Hosted Flow delivery model
- Rules & Conditions — The logic layer inside a workflow
- Evaluations — The runtime execution of a workflow
Updated about 1 month ago