110 likes | 230 Vues
Today's session by Dan Davis and Madhuri Bhogadi focuses on the standardization of notification systems within our activities framework. We will discuss how notifications are now being integrated across major tables and actions in the system. A new Notification Tab will be introduced to enhance user experience and efficiency. Notifications can be automated or manual, associated with various activities and user-defined groups, ensuring all relevant stakeholders are notified. Examples include alerts for credit limits and scheduled notifications for insurance expirations.
E N D
User Input Session Activities & Notifications Presented by: Dan Davis & Madhuri Bhogadi
Standardization • Notifications exist in the system now, we are going to standardize how and when they happen. • Allowing for notifications to be associated with any major table / action.
Standardization • Notification Tab will be added to Activity • Though out System we will allow for notifications along with activities
Standardization • Notifications will be triggered off of activities (Action) table • Tab in action maintenance will allow for notification by division by notification group • Notifications can be automatic or manual
Standardization • Notification groups currently allow for any number of people to be notified with either an alert or email. • We will add Entry to any email address and not only system Users
Types of Notifications • 1) Modulo (Open for discussion) • 2) Master Screen (Customer / SO / etc.) • 3) Scheduler Based (Based on a selection of data and placed on scheduler) • All can be Manual or Auto assigned
Examples • Credit limit exceeded. Allowed to be controlled by customer. Currently it is for all or none. • Tech finishes call. Allowed to be by SO or by customer. Can be auto or manual • SO or Job is received. Currently system controlled but will be standardized by activity. • New call created. Auto notify by customer • Notify when Insurance is expiring Scheduled Notification