Catalogs

Overview

The Catalogs feature in timveroOS provides a configuration system for defining and managing various business parameters, reference data, and dropdown values used throughout the platform. This enables administrators to modify system behavior without code changes.

Business Context

The Catalogs feature allows financial institutions to manage dynamic configuration data such as:

  • Department definitions for workflow routing

  • Reference rates for calculations

  • Dropdown values for forms

  • Business-specific categorizations

  • Rejection reasons for analytics

Catalog Types

Decision Departments

Configure departments for manual review routing.

Departments include:

  • Department Code: Unique system identifier

  • Description: Human-readable department name

  • Activity Status: Enable/disable departments

Example departments from documentation:

  • Underwriting Department

  • KYC Department

  • AML Department

  • Financial Department

Reference Rates

Manage rates used in pricing calculations:

Reference Rates
Reference rate catalog configuration interface

Configure:

  • Rate identifiers

  • Current values

  • Effective dates

  • Rate descriptions

Custom Catalogs

Create catalogs via the SDK for any business need:

  • Fee structures

  • Document types

  • Rejection reasons

  • Industry classifications

  • Geographic regions

Managing Catalogs

Adding Catalog Entries

Catalog Entry
Adding new entries to catalogs

Methods for populating catalogs:

  • Manual entry through interface

  • Bulk import capabilities

  • API integration options

  • Copy from existing entries

Catalog Maintenance

  • Edit existing entries

  • Activate/deactivate records

  • Track modification history

Form Builder Integration

Catalogs integrate with the Form Builder for dynamic dropdowns:

Form Integration
Using catalog values in form configuration

Form fields can reference:

  • Department lists

  • Rejection reasons

  • Document types

  • Custom value lists

System Integration

Workflow Integration

Catalogs are used in workflows for:

  • Department routing in warning facts

  • Reference data in calculations

  • Decision criteria values

  • Status definitions

Reporting Integration

  • Categorize data using catalog values

  • Filter reports by catalog entries

  • Track usage of catalog items

  • Analyze trends by categories

Pricing Integration

  • Reference rate lookups

  • Fee structure definitions

  • Margin calculations

  • Regional adjustments

Common Use Cases

Department Management

Configure organizational structure:

  • Create specialized review teams

  • Enable seasonal departments

  • Manage workload distribution

  • Track departmental performance

Rejection Reason Tracking

Standardize decline codes:

  • Regulatory compliance reasons

  • Credit policy violations

  • Documentation issues

  • Business rule failures

Geographic Configuration

Manage regional variations:

  • State-specific requirements

  • Regional risk factors

  • Local compliance rules

  • Market-based pricing

Configuration Guidelines

Naming Conventions

  • Use clear, descriptive names

  • Maintain consistent formatting

  • Avoid special characters

  • Document abbreviations

Data Management

  • Regular data validation

  • Archive obsolete entries

  • Monitor usage patterns

  • Update as needed

Access Control

  • Restrict editing permissions

  • Log all modifications

  • Review access regularly

  • Implement approval workflows

Best Practices

Catalog Design

  • Plan structure before creation

  • Consider future growth

  • Use appropriate data types

  • Implement validation rules

Maintenance Schedule

  • Regular review cycles

  • Data quality checks

  • Usage analysis

  • Performance monitoring

Documentation

  • Catalog purpose statements

  • Field descriptions

  • Usage instructions

  • Change history

Technical Considerations

Performance

  • Catalogs cached for efficiency

  • Indexed for quick searches

  • Optimized for frequent access

  • Monitored for size limits

Data Integrity

  • Referential integrity maintained

  • Cascade rules for updates

  • Validation at entry point

  • Consistency checks

Audit Trail

All catalog changes tracked:

  • User identification

  • Timestamp

  • Previous values

  • Change reasons

Troubleshooting

Common Issues

Catalog Values Not Appearing

  • Verify catalog is active

  • Check integration configuration

  • Review user permissions

  • Clear system cache

Update Not Reflecting

  • Confirm save successful

  • Check for validation errors

  • Review approval status

  • Verify cache refresh

Performance Issues

  • Monitor catalog size

  • Review usage patterns

  • Check indexing

  • Optimize queries

Integration Points

Catalogs connect with:

  • Workflows: Reference data and routing

  • Forms: Dropdown populations

  • Pricing: Rate references

Next Steps

With catalogs configured, explore:


For additional catalog configuration support, consult your implementation team or system documentation.

Last updated

Was this helpful?