 |
 |
|
| Monday, July 2 2007 9:55am |
|
Received another report with the wrong date. Date should have been the 6/30, but showed up as 7/1, we accessed it on 7/2. Is it possible that the system is auto-applying the date the report is sync'd as the date of service? or maybe this person didn't enter the report until the next day and forgot to change the service date? |
| admin (Tuesday, July 3 2007 7:04pm) |
=== Forwarded Ticket # 939033 === (Deleted due to Duplcate)===
Wednesday, June 20 2007 11:48am from Becky
Hi Kurt, the dates are not coming over correctly on the Tablet reports. There is one in the queue right now that automatically assigned the 18th when we know that it was done on the 17th
(Thursday, June 21 2007 1:12am) Kurt Jensen
I'm not sure what is causing this and I'm not sure we can solve this without some help from Zoll. |
|
| admin (Tuesday, July 3 2007 7:04pm) |
The Tablet program does not have a "Date of Service" field. This report data is derived from several different other possible fields. When a creating the printable report from the data the following fields are examined in order and the first one to contain a date is used:
- FDC_Trips.atsdate (At Scene Date)
- FDC_Trips.enrdate (En route Date)
- FDC_Trips.dispdate (Dispatched Date)
- FDC_Trips.calldate (Call Date)
- FDC_Trips.tdate (Trip Date)
I believe the "Trip Date" is set when the user adds the new call from the inbox screen.
It seems that this problem is most prevalent when a user starts a report after the call is finished.
If the tablet user adds the new report when they leave the station this will most likely stamp the correct time into (Trip Date).
Right now I am thinking that we should turn on the En route Time field and allow people to set a time there that "Date of Service" can feed off of that.
Billers should still be able to adjust this later to correct times when they receive dispatch reports.
|
|
|
|
|
| Copyright © 2003-2004 osTicket.com,
All Rights Reserved. |
|
|
