Notification
Overview
Notification – Business Overview
Notification is used in Dafater to automatically keep people informed when specific business events happen. It ensures that the right users receive timely messages when important actions occur, such as approvals, status changes, or upcoming deadlines. This helps organizations stay proactive, reduce manual follow-ups, and maintain clear communication across teams.
What Notification Is Used for in Business Operations
Notification allows a business to: - Automatically inform employees, managers, or stakeholders about important events - Ensure critical actions are not missed (for example, approvals or escalations) - Maintain transparency and accountability across processes - Reduce reliance on manual emails or reminders
In simple terms, Notification acts as an automated alert system that supports smooth day-to-day operations.
Prerequisites and Setup Requirements
Before using Notification effectively, the following should be in place: - Business processes must be clearly defined (for example, approval flows or status changes) - Users and roles should already exist in Dafater - Email communication should be enabled and aligned with company policies - Clear ownership of each process, so notifications reach the correct people
Without these basics, notifications may be sent to the wrong users or fail to support business goals.
Typical Workflow and Business Fit
A typical business flow using Notification looks like this: 1. A business event occurs (such as a document being created, approved, or updated) 2. Notification checks whether this event requires communication 3. A message is automatically sent to the relevant users 4. Recipients take timely action based on the message received
This workflow fits naturally into daily operations by acting in the background, ensuring communication happens without extra effort.
Key Business Scenarios Where Notification Is Essential
Notification is especially valuable in scenarios such as: - Approval processes where managers must be informed immediately - Compliance-driven activities that require timely awareness - Customer-facing processes where delays impact service quality - Internal coordination across departments (finance, sales, operations, etc.) - Deadline-driven tasks where reminders prevent missed commitments
In these cases, Notification helps protect the business from delays, errors, or oversight.
Important Considerations for Users
When using Notification, users should keep in mind: - Messages should be clear, relevant, and actionable - Too many notifications can cause alert fatigue, reducing effectiveness - Notifications should align with business priorities, not personal preferences - Regular reviews are recommended to ensure notifications remain useful as processes evolve
Used thoughtfully, Notification becomes a powerful tool that strengthens communication, improves responsiveness, and supports better decision-making across the organization.
Basic Information
- Module: Email
- Document Type: System
Fields
| Field Name | Label | Type | Required | Options | Description |
|---|---|---|---|---|---|
| enabled | Enabled | Check | - | Activate or deactivate this notification rule in Dafater | |
| is_standard | Is Standard | Check | - | Indicates whether this is a Dafater standard notification | |
| module | Module | Link | Module Def | Dafater module where this notification is applicable | |
| channel | Channel | Select | ✓ | Email, Slack, System Notification, SMS | Delivery channel used by Dafater to send notifications |
| slackwebhookurl | Slack Channel | Link | Slack Webhook URL | Linked Slack webhook for sending Dafater alerts | |
| subject | Subject | Data | - | Notification subject line shown to recipients | |
| event | Send Alert On | Select | ✓ | , New, Save, Submit, Cancel, Days After, Days B... | Document event that triggers the Dafater notification |
| document_type | Document Type | Link | ✓ | DocType | Dafater document type monitored for this notification |
| method | Trigger Method | Data | - | Custom Dafater method executed to trigger notification | |
| date_changed | Reference Date | Select | - | Reference date field used for date-based alerts | |
| daysinadvance | Days Before or After | Int | - | Number of days before or after reference date | |
| value_changed | Value Changed | Select | - | Field whose value change triggers notification | |
| sender | Sender | Link | Email Account | Email account used by Dafater to send messages | |
| sendsystemnotification | Send System Notification | Check | - | Send in-app Dafater system notification | |
| sender_email | Sender Email | Data | Email address shown as message sender | ||
| condition | Condition | Code | - | Logical condition controlling when notification is sent | |
| html_7 | html_7 | HTML | Condition Examples: ,Reference examples for writing notification conditions |
| |
| setpropertyafter_alert | Set Property After Alert | Select | - | Document property updated after notification is sent | |
| property_value | Value To Be Set | Data | - | Value assigned to the selected document property | |
| sendtoall_assignees | Send To All Assignees | Check | - | Send notification to all assigned users | |
| recipients | Recipients | Table | Notification Recipient | List of users or roles receiving notifications | |
| message_type | Message Type | Select | Markdown, HTML, Plain Text | Format used for notification message content | |
| message | Message | Code | Jinja | Notification message template with dynamic Dafater data | |
| message_examples | Message Examples | HTML | Message Example, ,<h3>Orde... |
Sample templates demonstrating notification message usage | |
| view_properties | View Properties (via Customize Form) | Button | - | Open Customize Form to manage view properties | |
| attach_print | Attach Print | Check | - | Attach document printout with the notification | |
| print_format | Print Format | Link | Print Format | Print format used for attached document |
Child Tables
Recipients (Notification Recipient)
| Field Name | Label | Type | Required | Options | Description |
|---|---|---|---|---|---|
| receiverbydocument_field | Receiver By Document Field | Select | - | Select document field containing recipient email or user | |
| receiverbyrole | Receiver By Role | Link | Role | Send notification to all users assigned selected role | |
| cc | CC | Code | - | Additional recipients copied on notification communications | |
| bcc | BCC | Code | - | Hidden recipients receiving notification without visibility to others | |
| condition | Condition | Data | - | Logical condition controlling when recipient receives notification |
Permissions
| Role | Read | Write | Create | Delete | Submit | Cancel |
|---|---|---|---|---|---|---|
| System Manager | ✓ | ✓ | ✓ | ✓ |
Related DocTypes
| DocType | Relationship | Module |
|---|---|---|
| Email Account | Links to | |
| Module Def | Links to | Core |
| Print Format | Links to | Printing |
| Slack Webhook URL | Links to | Integrations |