/
Work Order Status History - Discrepancy Between Effective Date and Changed on Time


Work Order Status History - Discrepancy Between Effective Date and Changed on Time

Issue/Symptom/Question

Times for status change and effective date of change vary by exactly 1 hour. Linux server time is correct, time on each of the RDP machines also appears correct.

Applies To

Penta for Windows

Service Management > Work Orders > Status History

Resolution/Fix/Answer

Work Order status time is pulled from the database setting in DBTIMEZONE. This setting does not get updated for daylight savings time so, the difference will be seen when we change our clocks. It’s a static setting of -X.00 from UTC, depending on the database time zone.

The workaround is by setting the timezone for the OU, which will override DBTIMEZONE. Updating the OU timezone will automatically adjust as we move into and out of daylight savings time. Once you make this update, any future statuses changes will have the times matching. Previous times are not adjusted.