List of Data Validations
The following validations are performed for optimization jobs, for the specified types of data.
Type of Data
Validation
Work Order
The Service Duration field should not contain zero or a negative value.
If the work order is not a multi-day work order, the service duration cannot be more than one day.
The Importance field should not contain zero or a negative value.
If the work order belongs to a dependency group, the Dependency Type field value should not be empty.
The PST value should not be after the PET value.
If the work order is a Lock in Place work order, the assigned resource must not be empty.
If the work order is a locked schedule work order, it should not have more than one access hour entry.
If the work order is a locked schedule work order (lock in place or lock to arrival window), Service Duration should fit in the work order access hour duration.
If the work order specifies a required expertise, the expertise level should be one or higher.
If the work order belongs to a dependency group, it should either be a primary or a secondary work order.
If the work order belongs to a dependency group, both Time or Resource dependency can not be NONE at the same time for a relation.
If the work order belongs to a dependency group and the dependency relation type is Start Unison or Finish Unison, the minimum time buffer value should not be negative values.
If the work order belongs to a dependency group and the dependency relation type is Start Unison, Finish Unison, or Start to Finish, the resource dependency type should not be Same Resource.
The work order must either have valid geolocation or valid address information.
If the work order contains the geolocation information, the latitude-longitude coordinates must be valid.
The Business Hours field should not be empty.
If the Optimize for Single Day option is enabled for the dispatch process, the SLA fields (Preferred Start Time and Preferred End Time) should be within a day. Also, the work order must have only one Access Hours value.
The Business Hours should have both start and end time values.
The Business Hours start time value should be earlier than the end time value.
Event
The Event Duration field should not contain zero or a negative value.
The Assigned Resource field should not be empty.
The Event Type field should not be empty.
If the event type is CALENDAR_GEO_ITEM or BREAK_GEO_ITEM, the event should have either valid geolocation or valid address information.
The Business Hours field should not be empty.
There should be only one Business Hours field value.
The Business Hours should have both start and end time values.
The Business Hours start time value should be earlier than the end time value.
If the event contains the geolocation information, the latitude-longitude coordinates must be valid.
Event Business Hours must intersect with the technician's working hours.
Technician
The Business Hours field should not be empty.
The technician record must have valid geolocation or address information.
The Business Hours should have both start and end time values.
The Business Hours start time value should be earlier than the end time value.
If the technician record contains the geolocation information, the latitude-longitude coordinates must be valid.
If the Drive Before Shift Start or Drive After Shift End values are provided for the dispatch process or the technician, the values should not be negative.
The Max Hours field should not contain zero or a negative value.
The Maximum Distance field should not contain zero or a negative value.
The Overtime Tolerance field should not contain zero or a negative value.
The Average Travel Speed field should not contain zero or a negative value.
If there is an expertise, the expertise level should be one or higher.
If there is an expertise and the Valid From and Valid To fields are not null, the Valid To date must be later than the Valid From date.
If the Current Address value is present, it must have valid geolocation or address information.
If the Current Address contains the geolocation information, the latitude-longitude coordinates must be valid.
Overnight stay and single-day optimization features are mutually exclusive. The technician is not considered for scheduling if both are enabled.
Was this helpful?