Warning & Alert Configuration

Overview

This guide covers the configuration of Warning Facts and Alert Facts that trigger manual review processes in timveroOS. Proper configuration ensures that cases requiring human judgment are routed to the appropriate departments with the necessary context and forms for decision-making.

Warning Facts vs Alert Facts

Warning Facts (Manual Review)

Warning Facts create manual review requirements that:

• Route to specific departments for human decision

• Require explicit approval or decline

• Can include data collection forms

• Block process progression until resolved

Alert Facts (Automatic Decline)

Alert Facts trigger automatic actions:

• Immediately decline applications

• Record standardized decline reasons

• Trigger adverse action notifications

• Do not require manual review

Department Configuration

Setting Up Decision Departments

Departments are the organizational units that receive and process Warning Facts.

Navigation: Settings → Catalogs → Decision Departments

Creating a Department:

1. Click Add

2. Configure:

   • Code: Unique identifier (UPPERCASE, no spaces) - e.g., UNDERWRITING

   • Description: Human-readable name - e.g., Underwriting Department

   • Status: Active/Inactive

3. Click Save

Standard Department Examples:

Code	Description	Typical Responsibilities
UNDERWRITING	Underwriting Department	Credit analysis, financial assessment
KYC	KYC Department	Identity verification, documentation review
AML	AML Department	Transaction patterns, compliance review
FINANCIAL	Financial Department	Complex financial analysis

Assigning Users to Departments

Users must be assigned to departments to see Warning Facts in their Launchpad queue.

Navigation: Settings → Users → [Select User]

1. Execute action: Update Department

2. Select department from dropdown

3. Save

Note: Users can only be assigned to one department at a time.

Configuring Warning Facts in Workflows

Adding Warning Facts to Workflows

Warning Facts are created using the "Save Warning Fact" node in the Workflow Designer.

Navigation: Settings → Workflows → [Select Workflow]

Step 1: Add Save Warning Fact Node

1. Drag "Save Warning Fact" from the Tasks panel

2. Connect to appropriate workflow position

3. Configure the node

Step 2: Configure Warning Fact Fields

Field	Description	Required
Name	Internal identifier for the workflow tool	Yes
Fact	Display name shown on application/participant	Yes
Decision Department	Department that will review (from catalog)	Yes
Form Scheme	Form code for data collection (from Form Builder)	No

Example Configuration:

Name: Income Verification Required
Fact: Income Verification Required
Decision Department: UNDERWRITING
Form Scheme: income_verification

Conditional Warning Facts

Configure Warning Facts to trigger based on conditions:

IF credit_score < 650 AND income_verified = false
  → Create Warning Fact: "Low Credit Score - Manual Review"
  → Assign to: UNDERWRITING
  → Form: credit_review_form

Form Integration

Linking Forms to Warning Facts

Forms collect data during Warning Fact resolution.

Step 1: Create Form in Form Builder

See Form Builder for detailed instructions.

Step 2: Note Form Code

After saving, copy the form code (e.g., income_verification)

Step 3: Link to Warning Fact

In the Save Warning Fact node, enter the form code in the Form Scheme field.

Form Data Flow

When a reviewer completes a form during Warning Fact resolution:

1. Form data validates according to Form Builder rules

2. Data updates participant/asset profile

3. Updated data flows to downstream processes (pricing, documents)

4. Warning Fact status changes to Resolved

Configuring Alert Facts

Setting Up Decline Reasons

Alert Facts use predefined decline reasons from the catalog.

Navigation: Settings → Catalogs → Decline Reasons

Creating a Decline Reason:

1. Click Add

2. Configure:

   • Code: Unique identifier

   • Description: Decline reason text

   • Status: Active/Inactive

3. Click Save

Common Decline Reasons:

• Credit score below minimum threshold

• Income verification failed

• Fraud risk detected

• Regulatory compliance violation

• Documentation incomplete

Adding Alert Facts to Workflows

Step 1: Add Save Alert Fact Node

1. Drag "Save Alert Fact" from Tasks panel

2. Connect to workflow position

3. Configure the node

Step 2: Configure Alert Fact Fields

Field	Description	Required
Alert Type	Select from Alert Facts catalog	Yes
Stop Workflow	Whether to halt workflow execution	No

Example Configuration:

IF fraud_score > 0.8
  → Create Alert Fact: "High Fraud Risk"
  → Stop Workflow: Yes

Multi-Department Routing

Parallel Department Processing

Configure workflows to create Warning Facts for multiple departments:

Workflow: Loan Application Review

IF income_documentation_incomplete
  → Warning Fact to FINANCIAL department

IF identity_verification_failed  
  → Warning Fact to KYC department

IF credit_score < threshold
  → Warning Fact to UNDERWRITING department

Processing Rules:

• Each department handles their warnings independently

• Any department decline results in application decline

• All warnings must be resolved for approval

• Departments work in parallel

Escalation Configuration

Time-Based Escalation

Configure escalation rules for aging Warning Facts (SDK-level configuration):

• SLA thresholds for response times

• Escalation notifications

• Supervisor alerts

• Auto-assignment rules

Note: Escalation rules are configured at the SDK level. Contact your development team for escalation configuration.

Best Practices

Warning Fact Design

• Use clear, descriptive fact names

• Assign to appropriate specialized departments

• Include forms for data collection when needed

• Document expected resolution actions

Department Organization

• Align departments with organizational structure

• Define clear responsibilities per department

• Ensure adequate staffing for expected volume

• Monitor workload distribution

Form Configuration

• Design simple, focused forms

• Include only necessary fields

• Match field names to profile attributes exactly

• Test forms before deployment

Troubleshooting

Warning Facts Not Appearing in Launchpad

Possible Causes:

• User not assigned to correct department

• Department code mismatch in workflow

• Workflow not activated

• Warning Fact node not properly configured

Resolution: Verify department assignment, check workflow configuration, confirm activation status.

Forms Not Displaying

Possible Causes:

• Form code incorrect in Warning Fact configuration

• Form not saved/published

• Form deactivated

Resolution: Verify form code matches exactly, check form status in Form Builder.

Related Operations

Once configured, see how Warning Facts are used in operations:

• Manual Decisions (OPS) - Launchpad queue management and decision-making

Next Steps

With warning and alert configuration complete, explore:

• Form Builder - Create data collection forms

• Catalogs - Manage departments and decline reasons

• Workflow Fundamentals - Build workflow logic

---

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