Notifications
Understanding Notification Architecture
The system implements a mechanism for generating and sending notifications to various process participants when different events occur. This capability ensures timely communication throughout the lending lifecycle, supporting both operational efficiency and regulatory compliance.
Core Notification Concepts
To create and send a specific notification, the system user must configure a corresponding template. Several notification parameters are defined at the template level:
Template Parameters
Name: The identifier of the notification template
Event Type: The type of event that triggers notification generation and sending (configured at framework level)
Recipient: The type of subject for whom the notification is intended
Gateway Type: The notification delivery channel (SMS, Messenger, Email, Letter)
Subject: The notification subject line title
Late Send Available: Flag indicating possibility of late notification delivery (relevant for 24/7 processes)
Prevent Duplicate: Flag for controlling duplicate message sending to same recipient
Notification Content: Static text combined with variables for personalization
Recipient Types
By default, the system supports notifications to:
Bank Employees: Internal operational communications
Participants with Borrower Role: Primary applicant communications
Other Participant Roles: Guarantors, pledgors (with framework configuration)
Application Responsible Managers: Process ownership notifications
Content Configuration
Notification content utilizes:
Static Text: Fixed message components
Variable Substitution: Dynamic content from system data
Personalization Elements: Recipient-specific information
System-Provided Hints: Assistance for variable usage
The template can be extended with fields for more fine-tuned notification configuration. For example, when setting up a notification template with event type "Participant Status Change," users must fill in an additional Status field to specify which participant status transition should trigger the notification.
Employee Notification Management
The notification mechanism has specific functionality for financial institution employees who don't have explicit connection to the specific object triggering the notification:
Subscription-Based Notifications
Create templates with recipient "organization employees"
Configure user subscriptions on user creation/editing forms
Users receive notifications based on subscription preferences
Enables department-wide or role-based communications
This approach ensures relevant staff members stay informed about process events even when not directly assigned to specific applications.
Configuration Examples from Documentation
Example 1: Loan Application Approval
Client notification when their loan application receives approval:
Event Type: Participant Status Change
Status: Approved
Recipient: Participant (Borrower)
Gateway: Email/SMS
Content: Congratulations message with next steps
Example 2: Manual Review Alert
Underwriting staff notification for applications requiring review:
Event Type: Participant Status Change
Status: Manual Review
Recipient: Organization Employees (subscribed)
Gateway: Internal messaging
Content: Review requirement with application details
Example 3: Disbursement Confirmation
Client notification of loan disbursement to account:
Event Type: Loan Disbursement
Recipient: Participant (Borrower)
Gateway: Email
Content: Disbursement details and amount
Implementation Requirements
Prerequisites
Before configuring notifications, ensure:
Gateway Integrations: Email server, SMS gateway, messaging platforms
Event Type Definition: Framework-level trigger configuration
Recipient Mapping: User and participant identification setup
Template Design: Content and variable planning
Gateway Integration
Corresponding integrations must be implemented for each delivery channel:
Email: SMTP server configuration
SMS: SMS gateway provider integration
Messenger: Platform-specific API setup
Letter: Document generation and delivery system
Variable Management
The system provides hints for working with variables:
Available data fields by context
Proper syntax for substitution
Null value handling
Formatting options
System Capabilities
Automated Triggering
Event-based notification dispatch
Status change monitoring
Time-based scheduling
Conditional logic support
Multi-Channel Delivery
Channel selection by template
Recipient preference respect
Fallback channel configuration
Delivery optimization
Tracking and Monitoring
Message generation logs
Delivery status tracking
Failed delivery handling
Analytics and reporting
Compliance Support
Regulatory notice automation
Delivery confirmation
Template versioning
Audit trail maintenance
Implementation Resources
Through the Admin Panel (Step 2)
Configure notifications through:
Notification Configuration - Template setup and management
User Management - Employee subscriptions
Through the SDK (Step 1)
For advanced configuration:
Event Configuration - Custom event types
Integration Development - Gateway connections
[Core embedded component] - Access management if fundamental for timveroOS, so it comes in the application be deafult, no need to add it in the SDK.
Key System Behaviors
Template-Driven Architecture
All notifications require configured templates
Templates define all notification parameters
Reusable across similar scenarios
Version controlled for compliance
Event-Based Execution
Framework-level event definitions
Automatic triggering on events
No manual intervention required
Consistent delivery timing
Flexible Recipient Management
Direct object participants
Subscription-based employees
Role-based routing
Dynamic recipient resolution
Related Topics
Status Management - Status change triggers
Document Management - Document-related notifications
User Management - Employee subscription configuration
timveroOS: Intelligent notification orchestration for lending operations
Last updated
Was this helpful?