Data Scanner Configuration for Jeopardy Detection
When you configure Data Scanners to identify Jobs in jeopardy in Service Board, be aware of the following details.
Predefined Inactive Data Scanner Records
Service Board ships with the following predefined inactive Data Scanner records for use as templates, which can be activated, but cannot be updated.
• Appointment Data Scanners
◦ The scheduled end time for the Appointment has been reached and work is not completed.
◦ The technician has not started work on the Appointment, and the scheduled time has passed.
• Job Data Scanners
◦ The preferred start time for the Job is getting close and no Appointments are scheduled.
Data Scanner Creation
• Service Board ships with the Captured by Data Scanner and Captured by Data Scanner On fields linked to the Job and Appointment objects by default.
• The In Jeopardy field in the Job object is selected when Captured by Data Scanner fields in Job records or in related Appointment records are selected.
• Updates to the Captured by Data Scanner, Captured by Data Scanner Updated On, and In Jeopardy fields do not trigger HTTP Notifications, and therefore cannot be synced to Salesforce.
• Severity field values in Data Scanner records are not visible to dispatchers.
Data Scanner Runs
• When users manually run full scans, or scans are automatically triggered after records are created, updated, or deleted, any records that are in violation of Data Scanner Rules are placed into jeopardy status. Users then receive email notifications of scan success or failure, and dispatchers receive browser notifications of the status changes.
• Service Board ships with two predefined inactive System Jobs, Scan Jobs and Scan Appointments. You can activate these System Jobs to scan Jobs and Appointments, or create your own custom System Jobs to run specific Data Scanners.