Notifications Table

This is where you create and schedule an actual notification, by associating a notification template record (from notify_templates table) with an action/event record (from activity_log table).

Field Description
notify_id Auto-numbered Primary Key of the table. Do not modify this field.
template_id
activity_log_id

Create a notification for a task/event by simply inserting a record in the table with the notify_templates Primary Key (template_id) and the activity_log Primary Key (activity_log_id) of the task/event/action item record.

is_active This field specifies whether the notification is active (1) or inactive (0). Newly created notifications would have a value of 1 to mark them active. The notifications WFR sets this field to 0 to deactivate the notification after the trigger condition has been met and the WFR has successfully sent the email(s). However, if notify_recurrence>0, then the WFR will not deactivate the notification as long as the trigger condition continues to be true AND the number of times the WFR has sent the email(s) has not exceeded the value in total_recurrence (if non-zero).

You can also manually deactivate a notification by setting is_active=0 in your logic, or allowing the user to do it in a view.
date_sent The WFR stores the date when it sent the email notification(s). When notify_recurrence>0, it stores the most recent date that it sent the email. Do not modify this field.
status_previous After execution, the WFR copies to this field the current value of activity_log.status. Do not modify this field.