Understand job start and end times calculations
Overview
There are a few start and end time fields relating to jobs in Skedulo. This article explains when they are initially set and when they are updated.
Skedulo field label | Field name | Description |
---|---|---|
Estimated Start (See note below) | sked__Estimated_Start__c | This field is initially populated when the job is allocated, based on the start time. Updated if the job is rescheduled. Updated when the job is set to “In Progress”. Updated when the job is set to “Complete.” |
Estimate End (See note below) | sked__Estimated_End__c | This field is initially populated when the job is allocated, based on the finish time. Updated if the job is rescheduled. Updated when the job is set to “In Progress.” Updated again when the job is set to “Complete.” |
Actual Start | sked__Actual_Start__c | Populated when the job is set to “In Progress.” |
Actual End | sked__Actual_End__c | Populated when the job is set to “Complete.” |
Start | sked__Start_c | The originally planned start time. Updated if the job is rescheduled. It does not change when the job is set to “In Progress” or “Complete.” |
Finish | sked__Finish_c | The originally planned finish time. Updated if the job is rescheduled. Does not change when the job is set to “In Progress” or “Complete.” |
Note
Skedulo displays “travel time” in the swimlanes calculated from the users home address to the first job, and afterward from job to job, using travel times retrieved through the underlying web mapping service API. There is no connection between the Skedulo web app swimlanes and these two “estimated” fields in Salesforce.Also, see the documentation on horizontal swimlanes (estimated travel) and job details (actual times).
Feedback
Was this page helpful?