Checklist Notifications
Administrators can enable user types or individual users to be notified in-app or via email at various points in the lifecycle of a checklist action by managing settings within Checklist Items and Notifications.
Notification Name | Description | Checklist Configuration Requirements | Notification Configuration Requirements |
|---|---|---|---|
Checklist Action Added | To alert users that checklist actions have been created and required attention. Sent immediately after the checklist actions is created. | No further configuration needed. | Must be enabled for in-app or email notifications. Recipients can be:
You can add any secondary recipients including user roles, role tags, users, and email addresses. |
Checklist Action Expired | To alert users that an individual checklist action has expired. Sent nightly once a checklist action has passed its expiration date. Sent to each recipient once. | Expiration must not be set to Never . Any other expiration setting applies. | Must be enabled. Only available for in-app notifications. Recipients can be:
You can add any secondary recipients including user roles, role tags, users, and email addresses. |
Checklist Action Expired Batch | To alert users that an individual checklist action has expired in batch email format. Sent nightly once a checklist action has passed it's expiration date. Sent to each recipient once. | Expiration must not be set to Never . | Must be enabled. Only available in email format. Recipients can be:
You can add any secondary recipients including user roles, role tags, users, and email addresses. |
Checklist Action Expired Escalation | To alert users that an individual checklist action has expired and there is a resulting escalation. Sent nightly once a checklist action has passed the days to notify in past the expiration. Sent to each recipient once. | Notification triggers based on the configuration of the Allow Auto Escalation field. | Only available for in-app notifications. Recipients include:
You can add any secondary recipients including user roles, role tags, users, and email addresses. |
Checklist Action Expired Escalation (Batch) | To alert users than an individual checklist action has expired and there is a resulting escalation in batch email format. Sent nightly once a checklist action has passed the days to notify in past the expiration. Sent to each recipient once. | Expiration must not be set to Never . Must select Allow Auto Escalation , set Days to Notify In , and select recipients. | Must be enabled. Only available in email format. Recipients are the users specified on the Allow Auto Escalation field.You can add any secondary recipients including user roles, role tags, users, and email addresses. |
Checklist Action Nearing Expiration | To alert users that an individual checklist action will expire in the future. Sent nightly once a checklist action has passed the Days Before Expiration Date. Sent to each recipient once. | Expiration must not be set to Never . Must select Notify When Nearing Expiration , set Days Before Expiration , and Roles to notify . | Only available for in-app notifications. Recipients are the users specified in the Notify When Nearing Expiration field.You can add any secondary recipients including user roles, role tags, users, and email addresses. |
Checklist Action Nearing Expiration (Batch) | To alert users that an individual checklist action will expire in the future in batch email format. Sent nightly once a checklist action has passed the days before expiration date. Sent to each recipient once. | Expiration must not be set to Never . Must select Notify When Nearing Expiration , set Days Before Expiration , and select recipients. | Must be enabled. Only available in email format. Recipients are the users specified on the Notify When Nearing Expiration field. |
Checklist Action Ready for Approval | Notify recipient that a checklist action is in Pending status and awaiting approval. | No further configuration needed. | Available in-app or email. Recipients include:
You can add any secondary recipients including user roles, role tags, users, and email addresses. |
Checklist Action Rejection | To notify recipients that a checklist action that was pending approval was rejected. Sent when the checklist action approver clicks the Reject button on a checklist action. Sent only once to each recipient. | The Approvals Required field must be selected on the checklist. A user must have taken action on the checklist action and submitted it for approval. | Must be enabled. Available in-app or email. Recipients are:
|
Checklist Action Waiting | To alert users that the checklist engine has run and new checklist actions require attention. Sent immediately after the checklist engine automatically creates new checklist actions based on the rules and settings of each checklist item. | No further configuration needed. | Must be enabled for in-app or email notifications. Recipients can be:
You can add any secondary recipients including user roles, role tags, users, and email addresses. |
Checklist Action Waiting (Contractor) | To alert contractors that the checklist engine has run and new checklist actions required attention. Sent immediately after the checklist engine automatically creates new checklist actions based on the rules and settings of each checklist item. | Contractor must be selected in the Action Required From field.The checklist must have a Timing of Post-Onboarding . | Must be enabled. Available in in-app or email format. No default recipients, but users can add additional recipients from the drop-down select filed. Contractor identified on the work order is the targeted recipient. |
Checklist Requirements Changed | Notify recipient if a user decided to modify the set of checklists from what is suggested based off of checklist criteria and job data. Triggered when conditions are met during Job Create and Job Edit. | No further configuration needed. | Only available for email notifications. Recipients include:
You can add any secondary recipients including user roles, role tags, users, and email addresses. |
Integration: Checklist Evidence Import Failure | Integration notification alerting that the checklist evidence import file was not run successfully. | Not directly linked to any action within VNDLY. Triggered only when the file has been run unsuccessfully and results are available in the File Transfer Reports section. | Available in in-app or email format. No default recipients, but users can add additional recipients from the drop-down select filed. |
Integration: Checklist Evidence Import Success | Integration notification alerting that the checklist evidence import file has run successfully. | Not directly linked to any action within VNDLY. Triggered only when the file has been run successfully and results are available in the File Transfer Reports section. | Available in in-app or email format. No default recipients, but users can add additional recipients from the drop-down select filed. |