Overview

This article gives you an overview of how iVendNext's Notification Engine helps automate routine tasks through alerts and reminders.

1. Core Notification Concepts

Key Components

• Triggers: Document events (submit, cancel, update)

• Recipients: Users, roles, or email groups

• Channels: Email, SMS, in-app alerts

• Conditions: Field-based logic for targeted alerts

Common Use Cases

• Approval request escalations

• Payment reminders

• Inventory threshold alerts

• Task assignment notifications

2. Setting Up Basic Notifications

Step-by-Step Configuration

1. Navigate to: Settings > Notifications > New

2. Define trigger conditions:

# Example: Trigger on overdue invoices

"condition": "doc.due_date < frappe.utils.nowdate() and doc.status == 'Unpaid'"

3. Configure delivery:

• Subject: "Urgent: Invoice {{ doc.name }} Overdue"

• Recipients: "Accounts Manager, Finance Team"

• Message: Include dynamic fields and action buttons

3. Advanced Notification Patterns

Conditional Escalation Matrix

Actionable Notifications

Embed direct links to:

• Approve/reject requests

• View related documents

• Process payments

<!-- Example action button -->

<a href="https://instance.ivendnext.com/approve?doc={{ doc.name }}" 

   style="background-color: #22C55E; color: white; padding: 8px 16px; text-decoration: none;">

   Approve Request

</a>

4. Integration with Workflows

Document Lifecycle Automation

1. Purchase Request → Notify approvers

2. Approval → Alert requester + procurement

3. GRN Creation → Trigger quality check

Timeout Handlers

# Auto-cancel unapproved requests after 48h

def check_pending_approvals():

    requests = frappe.get_all("Purchase Request", 

        filters={"status": "Pending", "creation": ("<", "frappe.utils.add_days(None, -2)")})

    for req in requests:

        frappe.db.set_value("Purchase Request", req.name, "status", "Cancelled")

        send_notification(req.name)

5. Best Practices

Notification Optimization

• Personalization: Use recipient's name and relevant context

• Throttling: Limit repeat alerts for same event

• Unified Templates: Maintain brand consistency

Avoiding Alert Fatigue

✔ Implement "Do Not Disturb" hours
✔ Provide opt-out options for non-critical alerts
✔ Consolidate related notifications

6. Monitoring & Analytics

Key Metrics to Track

• Delivery success rates

• Response times

• Click-through rates on action links

Continuous Improvement

1. Monthly review of notification effectiveness

2. A/B test message formats

3. Solicit user feedback on alert relevance