The following guide outlines what happens when the ‘planned return date’ is updated or defined.

Planned Return Date not populated

When the Planned return/off-hold date is NOT populated, then all Jobs from the On Hold Start Date onwards that are in a Pending Dispatch, Dispatched and Ready status will be changed to Cancelled

• The Job Allocation record status will be changed to Deleted
• A new “Resource” field (Look up to Resource) will be created on the Job and this will be populated with the Resource that was originally assigned to the Job
• If the Planned return/off-hold date is NOT populated and the Job is in Pending Allocation and the Current Date is Today then a batch job will run that will change the status to Cancelled with an Abort Reason of “Customer on Hold”
• When the On Hold flag is removed, these Jobs with Job Allocation status “Deleted”, will have a new Job Allocation record created for the Resource on the Job Record IF the resource is still Active. The Job will then be Pending Dispatch.
• If the resource is not active, the Job would be changed back to Pending allocation status.
• In addition to the Active status, the custom settings selected will be checked for conflicts – Unavailability, Resource Region (Primary or Secondary) = Job Region, Blacklisting, Activities, Job Conflicts.

Planned Return Date populated

When the Planned return/off-hold date is populated then all Jobs that fall within the On Hold Start Date and the Planned return/off-hold date that are in a Pending Allocation, Pending Dispatch, Dispatched and Ready status will be Cancelled with an Abort Reason of “Customer on Hold”

• The Job Allocation record status will be changed to Deleted (Not Applicable to Pending Allocation)
• A new “Resource” field (Look up to Resource) will be created on the Job and this will be populated with the Resource that was originally assigned to the Job (Not Applicable to Pending Allocation)
• When the On Hold is removed, these Jobs will have a new Job Allocation record created for the Resource on the Job Record IF the resource is still Active. The Job will then be Pending Dispatch
• If the resource is not active, the Job would be changed back to Pending allocation status.
• In addition to the Active status, the custom settings selected will be checked for conflicts – Unavailability, Resource Region (Primary or Secondary) = Job Region, Blacklisting, Activities, Job Conflicts.

Planned Return Date decreased

When the Planned return/off-hold date is decreased, then a batch will run to identify those Jobs that have been Cancelled with an Abort Reason of Customer on Hold with a Scheduled Start Date greater than the new Planned return/off-hold date

• These Jobs will have a new Job Allocation record created for the Resource on the Job Record IF the resource is still Active. The Job will then be Pending Dispatch.
• If the resource is not active, the Job would be changed back to Pending allocation status.
• In addition to the Active status, the custom settings selected will be checked for conflicts – Unavailability, Resource Region (Primary or Secondary) = Job Region, Blacklisting, Activities, Job Conflicts.

If the Job that was cancelled in a Pending Allocation status (had no resource attached to it), then these Jobs would be changed back to a Pending Allocation Status and the Abort Reason will be removed.

Planned Return Date increased

When the Planned return/off-hold date is increased, then a Batch will run to identify those Jobs that are in a Pending Allocation, Pending Dispatch, Dispatched and Ready Status with a Scheduled Start Date less than the new Planned return/off-hold date

• These Jobs will be Cancelled with an Abort Reason of “Customer on Hold”
• The Job Allocation record deleted (Not Applicable to Pending Allocation)
• The Resource will be populated on the Job (Not Applicable to Pending Allocation)