Automated Notifications

In OBS, there is a robust capability to set up various automated email notifications. These notifications can be fully customized to suit specific needs, allowing flexibility in defining who receives the notifications, when they are sent, what content they include, and under what conditions they are triggered. This ensures that users stay informed and processes run smoothly with minimal manual intervention.

1. Upcoming Task Deadline Reminder - 15 Days

This notification reminds users about tasks that are due in 15 days. The system checks for all unresolved tasks with a due date exactly 15 days from the current date. If a task is found, an email notification is sent to the task assignee and QA Managers. The email contains a table of all the tasks, including important details such as the task ID, change control code (if applicable), task name, status, assignee, and the number of days until the deadline.

• Frequency: Sent daily.
• Recipient: Task assignees and QA Managers.
• Content: A detailed table listing tasks due in exactly 15 days, with buttons to view or manage the tasks.

SQL Function: send_task_notification_15_days_before_deadline

Example Table

2. Overdue Task Summary - Weekly

This notification is sent every Friday and reminds users of overdue tasks that remain unresolved. The system checks for tasks that are past their due date and have not been marked as "Completed." The email contains a table of overdue tasks, including the task ID, change control code (if applicable), task name, status, assignee, and the amount of time the task has been overdue (in days, hours, or minutes).

• Frequency: Sent every Friday.
• Recipient: Task assignees and QA Managers.
• Content: A detailed table listing overdue tasks, with buttons to view or manage the tasks.

SQL Function: send_task_notification_overdue_friday

Example Table

3. Section 2 Pending Approvals (Change Request Coordination) - Daily

This notification reminds quality approvers about unresolved tasks in Section 2 of the Change Control process that require their review and approval. A detailed table lists all the pending tasks, including important details like the request ID, change control code, status, approver, and the date the request was made.

• Frequency: Sent daily at 6:00 AM.
• Recipient: Approvers assigned to the pending requests.
• Content: A table with requests that require attention, with buttons for approvers to access the requests directly in the system.

SQL Function: send_section_2_reminders_daily

Example Table