Using the time zone value of the Level 1 time segment
The Use Level 1 option in the Timezone list enables you to define time segments that use the time-zone value of the Level 1 time segment. If the Level 1 time segment has no time zone defined, the value of the server's time zone is used.
You can define a time segment that has its own time zone. Consider the time segments TS1, TS2, and TS3 in the following case:
- TS1 is available at Level 1 with the time-zone value of Asia/Calcutta.
- TS2 is unavailable at Level 2 with the time-zone value of Use Level 1. (TS2 uses the time zone of TS1.)
- TS3 is available at Level 3 with the time-zone value of Asia/Singapore. (TS3 has its own time zone.)
Sample schedule with the Use Level 1 option
Assumption: The AR System server is in the GMT + 5:30 - Asia/Calcutta time zone.
TimeSegment1:
- ID = Level1_Recurring_1_1_2000_8am_to_1_1_2031_5pm_Weekly_Once_Mon_ to_Fri_Asia_Calcutta
- Level = 1
- Availability = Available
- DurationType = Recurring
- StartDate = 1/1/2000
- StartTime = 8AM
- EndDate = 1/1/2031
- EndTime = 5PM
- Timezone = Asia/Calcutta
Result: The Schedule time remains 8 A.M. - 5 P.M. because the server and the Schedule are in the same time zone.
TimeSegment2:
- ID = Level2_Recurring_1_1_2000_10am_to_1_1_2031_11am_Weekly_Once_ Mon_to_Fri_Use_Level_1
- Level = 2
- Availability = Unavailable
- DurationType = Recurring
- StartDate = 1/1/2000
- StartTime = 10AM
- EndDate = 1/1/2031
- EndTime = 11AM
- Timezone = Use Level 1
Result: The Schedule time remains 10 A.M. - 11 A.M. because the server is in the Asia/Calcutta time zone and the Schedule (which uses the time zone of the Level 1 time segment) is in the Asia/Calcutta time zone.
TimeSegment3:
- ID = Level2_Recurring_1_1_2000_12pm_to_1_1_2031_1pm_Weekly_Once_ Mon_to_Fri_Asia_Calcutta
- Level = 2
- Availability = Unavailable
- DurationType = Recurring
- StartDate = 1/1/2000
- StartTime = 12PM
- EndDate = 1/1/2031
- EndTime = 1PM
- Timezone = Asia/Calcutta
Result: The Schedule time remains 12 P.M. - 1 P.M. because the server and the Schedule are in the same time zone.
TimeSegment4:
- ID = Level3_Avail_Recurring_1_1_2000_9am_to_1_1_2031_10am_Weekly_ Once_Mon_to_Fri_Australia_Sydney
- Level = 2
- Availability = Available
- DurationType = Recurring
- StartDate = 1/1/2000
- StartTime = 9AM
- EndDate = 1/1/2031
- EndTime = 10AM
- Timezone = Australia/Sydney
Result: The Schedule time is converted to ServerTime as 3:30 A.M. - 4:30 A.M. because the Schedule time zone Australia/Sydney is in DST with an offset of 5.50 (that is, 5 hours and 30 minutes).
Using the four time segments and the Add command, the Business Time command is
If startTime is 1/23/2008 1:00:00 AM, the following scenarios could occur:
- Case 1: If you add 1 second, the result is 1/23/2008 3:30:01 AM.
- Case 2: If you add 1 hour, the result is 1/23/2008 8:00:00 AM.
- Case 3: If you add 2 hours, the result is 1/23/2008 9:00:00 AM.
- Case 4: If you add 3 hours, the result is 1/23/2008 11:00:00 AM (10 AM-11 AM is Unavailable).
- Case 5: If you add 4 hours, the result is 1/23/2008 1:00:00 PM (10 AM-11 AM and 12 PM-1 PM are Unavailable).
- Case 6: If you add 7 hours, the result is 1/23/2008 4:00:00 PM (10 AM-11 AM and 12 PM-1 PM are Unavailable).
- Case 7: If you add 8 hours, the result is 1/24/2008 3:30:00 AM (10 AM-11 AM and 12 PM-1 PM are Unavailable).
The following figure illustrates this example.
Example of Use Level 1