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.

Navigation: Settings → Catalogs

Important: Admin Panel users can only add entries to existing catalogs. Creating new catalog types requires SDK development.

Available Catalogs

The following catalogs are available out-of-box:

Catalog	Purpose	Used By
Form Builder	Workflow warning resolution forms	Workflow Designer, Launchpad
BI Dashboards	Business intelligence dashboard definitions	Analytics & Reporting
Decision Departments	Manual review routing	Workflow warnings, Launchpad
Decline Reasons	Standardized rejection codes	Workflow alerts, Adverse action
Reference Rate	Interest rate benchmarks	Pricing calculations
Alert Facts	Automatic decline triggers	Workflow Designer
Warning Facts	Manual review triggers	Workflow Designer

Note: Each project may have additional custom catalogs relevant to that specific implementation. Custom catalogs are created via SDK.

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.

Fields:

Field	Description	Required
Code	Unique system identifier (UPPERCASE, no spaces)	Yes
Description	Human-readable department name	Yes
Status	Active/Inactive	Yes

Creating a Decision Department:

Step 1: Create Department

1. Navigate to: Settings → Catalogs → Decision Department

2. Click Add

3. Fill in:

   • Code: UNDERWRITING (unique, UPPERCASE, no spaces)

   • Description: Underwriting Department

4. Click Save

Step 2: Use in Workflow Tool

1. Open workflow (e.g., SoftHit/HardHit)

2. Add Save Warning Fact node

3. Configure:

   • Name: Income Verification Required (for Workflow Tool)

   • Fact: Income Verification Required (for Application)

   • Decision Department: UNDERWRITING (from dropdown)

   • Form Scheme: income_verification (optional)

Step 3: Save and Export Workflow

1. Save workflow

2. Mark workflow as ready for export

3. Import to Admin Panel and activate with Process Type Mapping

Step 4: Assign Department to User

1. Navigate to: Settings → Users → [Select User]

2. Execute action: Update Department

3. Select department from dropdown

4. Save

Example Departments:

• Underwriting Department

• KYC Department

• AML Department

• Financial Department

Reference Rates

Manage interest rate benchmarks used in pricing calculations:

Reference rate catalog configuration interface

Fields:

Field	Description	Required
Code	Unique rate identifier (e.g., SOFR, EURIBOR, LIBOR)	Yes
Description	Rate description	Yes
Value	Current rate value	Yes
Date	Effective date for this rate value	Yes
Status	Active/Inactive	Yes

Creating a Reference Rate:

Step 1: Open Catalog

1. Navigate to: Settings → Catalogs → Reference Rate

Step 2: Create New Entry

1. Click Add

Step 3: Fill in Fields

• Code: Unique rate identifier (e.g., SOFR, EURIBOR, LIBOR)

• Description: Rate description

• Value: Current rate value

• Date: Select the date from which this rate value is effective

Step 4: Save

Usage in Pricing:

Users can reference configured rates when configuring floating rates on products or additives by creating expressions such as SOFR+5. The system will provide suggestions for configured interest rate indicator code values.

Decline Reasons

Standardize rejection codes for analytics and compliance:

Fields:

Field	Description	Required
Code	Unique reason identifier	Yes
Description	Human-readable reason	Yes
Status	Active/Inactive	Yes

Common Decline Reasons:

• Credit score below threshold

• Income verification failed

• Documentation incomplete

• Fraud risk detected

• Regulatory compliance violation

Managing Catalogs

Adding Catalog Entries

Adding new entries to catalogs

1. Navigate to: Settings → Catalogs → [Select Catalog]

2. Click Add

3. Fill in required fields

4. Click Save

Catalog Maintenance

Action	Available	Notes
Add entries	✓	Click Add button
Edit entries	✓	Select entry, modify fields
Delete entries	Depends	Some catalogs allow deletion, others only deactivation
Deactivate entries	✓	Set Status to Inactive
Bulk import	✗	Not available
Create new catalog types	✗	SDK only

Form Builder Integration

Catalogs integrate with the Form Builder for dynamic dropdowns:

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

Admin Panel vs SDK Responsibilities

Capability	Admin Panel	SDK
Add entries to existing catalogs	✓
Edit catalog entries	✓
Deactivate entries	✓
Create new catalog types		✓
Define catalog structure		✓
Configure where catalogs are used		✓
Configure bulk import		✓

Next Steps

With catalogs configured, explore:

• Form Builder - Use catalogs in forms

• Warning & Alert Configuration - Use departments in warning routing

• Workflow Fundamentals - Use catalogs in workflows

• BI Catalog Management - Configure dashboards

---

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