Configuration Approach

Configuration Methods

TimveroOS separates business logic from code through three configuration levels:

1. SDK Configuration

What it configures:

  • Data model structure (entities, attributes, relationships)

  • Business Processes (application journey stages)

  • Status definitions and transitions

  • Core integrations (data sources, payment gateways)

Who configures: Development team

Documentation:

2. Admin Panel Configuration

What it configures:

  • Credit Products and Additives

  • Workflows (decision flows) using Workflow Tool

  • Mappings for data transformation

  • Document templates

  • Notification templates

  • Users and roles

Who configures: Business administrators

Documentation:

3. Operational Configuration

What it configures:

  • Individual application handling

  • Manual decision making

  • Document uploads

  • Exception processing

Who configures: Operations staff

Configuration by Component

Credit Products

  • SDK: Product entity structure

  • Admin Panel: Product parameters (amounts, rates, terms), Offer Engine scripts

  • Operations: Product selection during application

Credit Products Configuration

Decision Workflows

  • SDK: Workflow execution engine setup, Data Source connections

  • Admin Panel: Workflow design, Mappings, decision thresholds

  • Operations: Manual review decisions

Workflow Configuration

Document Management

  • SDK: Document entity structure, required document rules

  • Admin Panel: Document templates, generation triggers

  • Operations: Document upload and verification

Document Configuration

Notifications

  • SDK: Notification events definition

  • Admin Panel: Notification templates, delivery channels

  • Operations: N/A (fully automated)

Notification Configuration

Configuration Workflow

For new features:

  1. Development team sets up SDK entities and integrations

  2. Business administrators configure products, workflows, and templates

  3. Operations staff use configured system for daily work

For changes to existing features:

  • Minor changes (thresholds, templates): Admin Panel only

  • Major changes (new data sources, entity changes): SDK + Admin Panel

Implementation Resources

Through SDK (Development team)

Through Admin Panel


TimveroOS: Three-layer configuration for lending automation

Last updated

Was this helpful?