This approach directly addresses the client's requirement to have the Dispatcher Console reflect actual work times, which enables dispatchers to utilize newly available time slots (white space). By creating custom fields to store the original scheduled times, it preserves critical data for reporting on schedule adherence and planning accuracy. Automating the update of both Scheduled and Actual times via a Field Service Mobile flow simplifies the process for the field worker, tying it to the standard status change workflow. Finally, advising the client about potential update delays due to offline work sets realistic expectations about the system's behavior, which is a crucial part of a consultant's role.

B: This suggests a manual process using custom actions, which is less efficient and more prone to user error than an automated flow. Standard functionality already populates actual times based on status changes, making this approach redundant.

C: While correctly identifying that overwriting scheduled times is not a best practice for reporting, this option fails to provide a solution to the client's stated business requirement of visualizing white space on the Gantt.

D: This option is incomplete because it overwrites the original scheduled times without preserving them. This would prevent Universal Containers from ever being able to report on key metrics like schedule adherence or planning accuracy.

1. Service Appointment Life Cycle & Field Updates: The standard behavior is for Actual Start and Actual End to be populated upon status changes. To modify the Scheduled Start and Scheduled End fields

which control the Gantt display

custom automation is required.

Source: Salesforce Help

"Guidelines for Working with Service Appointments". See the section on status-based field updates.

2. Field Service Mobile Flows: Flows are the recommended tool for guiding mobile workers through complex business processes and automating record updates based on specific triggers or actions

such as changing a status.

Source: Salesforce Help

"Create Flows for the Field Service Mobile App". This document details the creation of flows that can update records from the mobile application.

3. Offline Behavior: Changes made in the Field Service mobile app while offline are queued and synchronized with the server once connectivity is restored. This explains the potential delay in the Dispatcher Console update.

Source: Salesforce Help

"How the Field Service Mobile App Handles Offline Work". See the section on "Data Sync".

4. Preserving Data for Reporting (Best Practice): A core KPI in field service is schedule adherence

which measures the difference between scheduled and actual times. Overwriting scheduled times without preserving the original values makes this analysis impossible. Creating custom fields to store the original plan is a standard implementation pattern to solve this.

Source: Salesforce Field Service Implementation Guide (PDF). While not a direct quote

the guide's sections on KPIs and Analytics (e.g.

Chapter 7: "Reports and Dashboards") implicitly rely on the existence of both planned and actual data for meaningful analysis.