Workflow Fundamentals
Overview
Workflow management in timveroOS provides a visual, low-code approach to automating decision logic. The system enables business users to design complex evaluation logic through a drag-and-drop interface while maintaining the flexibility to incorporate custom scripting when needed.
⚠️ Note: This documentation covers Workflow Engine workflows for automated decision-making, not business process flows. See Workflows vs Business Processes for clarification.
Critical Terminology Distinction
Workflow Engine Workflows (This Documentation)
Definition: Automated decision logic created in the visual Workflow Designer
Purpose: Evaluate data, make decisions, create warnings/alerts
Examples: Credit scoring, income verification, risk assessment
Configuration: Visual designer with tasks and logic components
Business Process Flows (Not Covered Here)
Definition: The overall journey of participants/assets through origination
Purpose: Define stages from application to funding
Examples: Application → Underwriting → Approval → Documentation → Funding
Configuration: SDK development using actions, events, and state machines
This documentation covers ONLY Workflow Engine workflows for automated decision-making.
Visual Workflow Designer
The workflow designer offers an intuitive interface for creating automated decision logic:

Core Components
The designer provides two main categories of components:

Tasks: Actions performed within the workflow
Expression - Execute calculations and logical operations
Load Datasource - Retrieve data from integrated sources or features from the Feature Store
Save to Profile - Store calculated values for downstream use
Save Alert Fact - Create automatic decline triggers
Save Warning Fact - Generate manual review requirements
Save Info Fact - Log information for audit purposes
Logic Functions: Control workflow execution
Switch - Create conditional branches based on criteria
Interrupt Workflow - Stop execution at specific points
Building Workflows
Basic Workflow Structure
Workflow Engine workflows are discrete evaluation processes that:
Execute at specific points in the business process
Retrieve and analyze data
Make automated decisions
Generate outcomes (approvals, declines, warnings)
Note: These workflows are evaluation tools, not the overall business process flow.
Data Source Integration
The Load Datasource task retrieves data from:
Connected external data providers
Features defined in the Feature Store

Example of retrieving credit bureau data:

Note: For creating reusable data transformations, see Feature Store.
Expression Configuration
Use expressions to implement business logic:

Conditional Logic
Implement branching logic using Switch components:

Decision Outcomes
Alert Facts (Automatic Decline)
Configure automatic decline triggers:

Alert facts:
Stop workflow execution (optional)
Record decline reason from configured catalog
Update application status
Trigger adverse action notifications
Warning Facts (Manual Review)
Create manual review requirements:

Warning facts include:
Department assignment for review
Form scheme for data collection
Contextual information
Profile Updates
Save calculated values to participant/asset profiles:

Profile data is used for:
Pricing calculations
Document filling
Product eligibility
Reporting and analytics
Workflow Mapping
Process Assignment
Map workflows to specific processes and participants/assets:


Multi-Stage Processing
Configure workflows for different evaluation stages, for example:
Soft Hit: Initial evaluation without external data
Hard Hit: Comprehensive evaluation with bureau data
Verification: Additional validation processes
Final Review: Last-stage quality checks
Profile Generation
Workflows automatically build comprehensive participant/asset profiles:

Generated profiles contain:
Credit assessment data
Income calculations
Risk indicators
Custom business metrics
Automation Through Entity Checkers
Entity Checkers are SDK-based automation tools that complement Workflow Engine workflows:
Key Distinction:
Workflow Engine: Visual, decision-focused workflows for evaluation
Entity Checkers: Code-based, event-driven automation for system reactions
How They Work Together:
Workflow Engine makes decisions (e.g., "approve loan")
Entity Checkers react to changes (e.g., "when loan approved, generate documents")
What Entity Checkers Do:
Monitor database changes in real-time
Execute business logic when conditions are met
Update related entities automatically
Trigger additional processing
Common Use Cases:
Start workflows when documents are complete
Update statuses based on payment receipt
Calculate derived values when data changes
Send notifications for specific events
Entity Checkers are NOT configured in the Workflow Designer but work alongside it. SDK development is required for Entity Checker implementation.
Error Handling
Data Availability
Handle scenarios where data is unavailable:
Configure fallback logic
Create warning facts for manual intervention
Log missing data for audit purposes
Continue processing where possible
Form Integration
When automated data retrieval fails:


Best Practices
Workflow Design
Start with simple, linear flows
Add complexity incrementally
Document logic within workflows
Use meaningful component names
Performance Considerations
Minimize external data calls
Implement efficient branching logic
Cache calculated values when possible
Monitor execution times
Testing Approach
Test with various participant profiles
Include edge cases and exceptions
Verify all branch paths
Validate profile updates
Maintenance
Version control workflow changes
Document business rule updates
Regular performance reviews
Monitor error frequencies
Common Patterns
Credit Evaluation
Load credit bureau data
Calculate credit metrics
Apply business rules
Generate decision outcome
Income Verification
Retrieve banking data
Analyze transaction patterns
Calculate verified income
Update participant profile
Risk Assessment
Gather multiple data sources
Calculate risk scores
Apply risk thresholds
Route to appropriate outcome
Integration Points
Workflow Engine workflows integrate with various system components through the participants and assets they evaluate:
Data Sources: External provider APIs for participant/asset data
Feature Store: Pre-configured data transformations for workflow use
Launchpad: Manual review queues for warnings
Document System: Template generation based on participant/asset requirements
Notification Engine: Status updates for participant/asset evaluation
Pricing Module: Offer calculations using participant profiles
Note: Workflows are triggered by participant and asset types, which are determined by product configuration.
Next Steps
With workflow fundamentals understood, proceed to:
Decision Automation - Configure automated decision logic
Manual Review Process - Set up human review workflows
Launchpad - Configure operational queues
For additional workflow configuration support, consult your implementation team or system documentation.
Last updated
Was this helpful?