FAQ: Why is the system sometimes auto-populating the "Dp" date in the "Service schedule" column?

FAQ: Why is the system sometimes auto-populating the "Dp" date in the "Service schedule" column?

There are two scenarios:

When a request is automatically dispatched to a Servicer (either by a fast track or recurring/PM instruction), the expected completion time (DP date) is populated to satisfy internally programmed create and dispatch rules.  The DP date will be reset (either to blank or whatever the Servicer optionally designates) when the Servicer reviews and accepts the request, so the Manager doesn't need to take any action to change it.

When a recurring/PM instruction is triggered and generates a request to the New Service Requests table, the DP date is populated with the occurrence date that was defined when the recurring request/PM was built.  This is done to satisfy internally programmed request creation rules.  The DP date will be reset to blank when the Manager dispatches the request.