We've long struggled with the drive and work timers not being more automated in the way they operate. The new Guided Workflow introduced in v47 seems to resolve some of the issues by enforcing their use, but creates other problems by introducing garbage data when one simply needs to review the ticket details or reschedule the ticket while not-on-site.
As the workflow acts now timers are started and stopped just to be able to review the ticket details. Additionally we'd like to be able to reschedule the ticket - including filling out the reschedule form and choosing appropriate delay-related close codes, without timer data being captured.
Put simply, we'd like to exclusively collect drive time and legitimate on-site work time data, without the inclusion of garbage drive/work timer data, in order to review or record the rescheduling of a ticket.
We've long struggled with the drive and work timers not being more automated in the way they operate. The new Guided Workflow introduced in v47 seems to resolve some of the issues by enforcing their use, but creates other problems by introducing garbage data when one simply needs to review the ticket details or reschedule the ticket while not-on-site.
As the workflow acts now timers are started and stopped just to be able to review the ticket details. Additionally we'd like to be able to reschedule the ticket - including filling out the reschedule form and choosing appropriate delay-related close codes, without timer data being captured.
Put simply, we'd like to exclusively collect drive time and legitimate on-site work time data, without the inclusion of garbage drive/work timer data, in order to review or record the rescheduling of a ticket.
0 Votes
0 Comments
Login or Sign up to post a comment