Sandbox Release Date |
December 13th, 2018 |
Production Release Date |
January 15th, 2019 |
Important
For those organizations who are on a Skedulo long term support arrangement—please check your sandboxes to see if this new package has been deployed successfully (the deployment will be performed on ***). If this package is not installed, you will need to make arrangements to deploy it manually to your sandboxes (to test) before *** (see Manual Installation Links).
Description |
|---|
|
When a resource is made inactive, future job allocations assigned to that resource are marked "Deleted" except for jobs that are "Complete" or "Cancelled." Refer to Allocating Jobs. |
|
When a resource is made inactive, future shift allocations of that resource are removed. Refer to Shifts. |
|
When a resource shift record is deleted, mark the parent shift as "Draft" if there are no more resources assigned to that shift. Refer to Shifts. |
|
Added field "Customer Confirmation Status" to the job object. A customer can be asked to confirm that they want a job to proceed. An API can be used to send an SMS message to the customer to request the confirmation. This field is for customer confirmation of the job (via SMS). |
Added object "Shift Tag" that allows adding tags to a shift record. |
|
Made some preparations for adding a field named "Estimated Travel Distance" to job allocations in Salesforce. Once fully completed, it can be used to compare estimated travel distances against actual travel distances. It’s calculated from the geolocated point the mobile user goes "En route" (or taps "Start Travel" on the Skedulo mobile app) to when they "Check in" to the job. |
Added validation for the field "Quantity" on job and resource requirements to be either null or greater than zero. |
It is no longer valid for a job to have resource requirements and allocations that do not have a resource requirement. In addition, it is also no longer valid for a job allocation to have a resource requirement which has a different job id than the job allocations. |
|
A resource requirement with job allocation time source set to false, can no longer set a relative start. A resource requirement with job allocation time source set to true must have a duration. A resource requirement with job allocation time source set to false now has its duration kept in sync with its job. A job allocation attached to a resource requirement that is not its time source now inherits its jobs time if it has job allocation time source set to true. |
Adding time to a "Queued" job that has an empty resource requirement will now correctly update the job status to "Pending Allocation." |
The field "Shift.IsDraft" now has the default value of true (checked). |
Made some preparations for a feature that will automatically update the geolocation for the address field on the following objects: job, activity, resource, and location. Once completed, the geolocation fields will be automatically populated based on the new address. |
Comments
0 comments
Article is closed for comments.