Configuration Sequence
Overview
Successful timveroOS implementation requires following a specific configuration sequence. This sequence ensures dependencies are properly established and system components build upon each other correctly.
System Context
Configuration sequence matters because many system components depend on others. For example, workflows require data sources to be configured first, and offer scripts need credit products to exist. Following the recommended sequence prevents configuration errors and rework.
Recommended Configuration Order
Step 1: System Foundation
User Roles and Permissions
Create organizational roles
Define permission sets
Establish department structure
Location: Settings → Users → Roles
Dependencies: None
Step 2: Reference Data
Catalogs Configuration
Decision departments
Decline reasons
Document types
Other business catalogs
Location: Settings → Catalogs
Dependencies: User roles (for department assignments)
Step 3: Document Templates
Generated Document Setup
Create document templates
Define merge fields
Configure generation triggers
Location: Settings → Documents → Templates
Dependencies: Catalogs (for document types)
Step 4: Credit Products
Product Definition
Create base products
Set product parameters
Define documentation requirements
Location: Settings → Credit Products
Dependencies: Document templates
Step 5: Data Integration
Data Source Configuration
Enable required providers
Configure authentication
Test connections
Location: Settings → Data Sources
Dependencies: Network connectivity, API credentials
Step 6: Feature Extraction
Mapping Creation
Define data extraction logic
Create feature calculations
Test transformations
Location: Settings → Feature Store
Dependencies: Data sources
Step 7: Decision Logic
Workflow Design
Build decision flows
Configure scoring logic
Set up manual review routing
Location: Workflow Tool
Dependencies: Mappings, catalogs
Step 8: Pricing Configuration
Offer Scripts
Create pricing algorithms
Link to additives
Test calculations
Location: Settings → Offer Engine
Dependencies: Credit products, workflow outputs
Step 9: Product Activation
Additive Creation
Configure product variants
Assign offer scripts
Activate for use
Location: Settings → Credit Products → Additives
Dependencies: Offer scripts
Step 10: Communication Setup
Notification Templates
Create message templates
Configure delivery channels
Set trigger events
Location: Settings → Notifications
Dependencies: SMTP/SMS gateway configuration
Step 11: Process Configuration
Business Process Setup
Define process flows
Link workflows to stages
Configure status transitions
Location: Framework level configuration
Dependencies: All previous components
Step 12: Testing and Validation
End-to-End Testing
Create test applications
Verify workflow execution
Validate offer generation
Location: Test environment
Dependencies: Complete configuration
Integration Points
Configuration sequence affects:
System Stability: Proper dependencies prevent errors
Testing Efficiency: Complete components before testing
Change Management: Minimize rework from sequence errors
Training Effectiveness: Train on fully configured system
Common Configurations
Example 1: Simple Consumer Lending
Sequence Focus: Basic flow without complex integrations
Roles and single department
Minimal catalogs
Basic loan agreement template
Single credit product
Credit bureau integration only
Simple credit score mapping
Basic approval workflow
Fixed-rate offer script
One additive
Email notifications only
Example 2: Multi-Product SME Lending
Sequence Focus: Complex products with multiple integrations
Multiple roles and departments
Extensive catalogs for industries/purposes
Various document templates
Multiple products (term loans, lines of credit)
Credit bureau + open banking + business data
Complex financial ratio mappings
Multi-stage workflows with manual reviews
Dynamic pricing scripts
Multiple additives per product
Multi-channel notifications
Technical Implementation Notes
Configuration sequence is enforced by:
System validation rules
User interface availability
Dependency checking
Reference integrity
SDK customization may affect sequence for:
Custom entity types
Modified business processes
Additional integration points
Extended validation rules
Note: SDK customization requires development resources. Consult your implementation team if standard sequence doesn't meet your needs.
Validation Checkpoints
After Each Major Step
Verify configuration saves successfully
Test individual component functionality
Document configuration decisions
Back up configuration data
Before Proceeding
Confirm dependencies are met
Validate test results
Obtain stakeholder approval
Update project documentation
Next Steps
Review complete sequence with project team
Identify any custom requirements
Create configuration checklist
Begin with system foundation
For additional support, consult your implementation team or system documentation.
Last updated
Was this helpful?