If Time Zones are not implemented, the answer to the question, “what time is it?” is answered by a call to the OS of the computer actually running SAMPro (typically a terminal server) to determine the system time.
However, if Time Zones are implemented in the User’s Branch record, the User’s time would calculated as the server’s time, plus or minus the Time Zone’s offset. This allows branch dispatchers from one time zone to log onto an application server in another time zone while still having dispatch times recorded in their local time.
Warning: Do Not Use Time Zone Offsets if the Scheduled Event / Report Manager Is Enabled
Since the Time Zone offset is applied to escalation events, Scheduled Events will not be correctly generated. For example, the user’s time of 1:30 is used for the time scheduled …. And the Scheduled Event manager runs the event at 1:30 PM – but the SEM’s 1:30 is 1:30 EST, and the User meant 1:30 PST. For this reason, Time Zones Offsets should not be used if Scheduled Events or Reports are enabled on your system.
Tip: Handling Scheduled Events for Different Zones
1. Do Not set up SAMPro Time Zone records with offsets.
2. A Terminal Server should be established for each Time Zone so that when the user logs in, the time will be correct for them without any need for an offset.
3. A Security setup will be needed so that Scheduled Events/Reports will be run by an agent-type User (with Security) on each Terminal Server.
The Time Zone in the User’s Branch record controls whether or not the time offset is applied.
Note the Time Zone specified in the User’s Branch record is used by the system when determining whether or not to apply an offset to the system time. This offset is applied to ALL date/time stamping operations, including journal entries, work order updates, and escalations. SAMPro Time Zone Offsets should NOT
Suppose User A in California logs onto a server in Cleveland running on Eastern time. The Branch Id specified in User A’s record references the Pacific Time Zone. If they create a Work Order at 1:30 PM Pacific Standard Time, it’s time of creation will be recorded as 1:30 PM. In addition, if they press the Spacebar in a time field to set the current time, the User’s time in California will appear.
Alternately, suppose User B in California logs onto a server in Cleveland running on Eastern time. The Branch Id specified in User B’s record does NOT specify a Time Zone. If they create a Work Order at 1:30 PM Pacific Standard Time, it’s time of creation will be recorded as 4:30 PM – the server’s time. In addition, if they press the Spacebar in a time field to set the current time, the server’s time in Cleveland will appear.
Time Zone Id:
A unique Id. This field is required (e.g., Eastern, Central, Pacific, etc).
Time Zone Name:
This optional field briefly describes the Time Zone.
The Following Fields Should NOT Be Completed if the Scheduled Event or Scheduled Report Managers are Enabled!
Daylight Savings Time Offset:
The Daylight Savings offset relative to server time. For example, if the server is located in the Eastern Standard Time zone, this field would be set to -3 for Pacific Time, -1 for Central Time and 0 for Indiana (no Daylight Savings Time). This field should be set to 0 for the zone in which the server is located.
Standard Time Offset:
The Standard Time offset relative to server time. For example, if the server is located in the Eastern Time zone, this field would be set to -3 for Pacific Time, -1 for Central and -1 for Indiana. This field should be set to 0 for the zone in which the server is located.