{//% unless portal.user.is_agent %} Tickets
Welcome
Login Submit a Ticket News {//% endunless %}

Add / Edit Location Details

The Add/Edit Locations screen allows you to add or edit Daylight Savings Time (DST) and Latitude/Longitude information for a location. You can also bulk edit DST information for multiple locations.


Graphical user interface, application 
Description automatically generated


Name:

  • Available when adding and is uneditable when bulk editing.

  • It is uneditable when editing a single location.

  • If bulk editing, the label is greyed out and the content is blank.

  • Validation is performed when adding a location, the system will check to see if the location already exists.

  • The system will inform the administrator if the location exists.

 

Latitude and Longitude:

  • The default latitude and longitude is 0.000 for each new location.

  • These values can be edited. if the value is not in the correct format or is not within the valid range, the following error message shows:

    • Must be a value between -90.000 and 90.000 (for latitude)

    • Must be a value between 180.000 and 180.000 (for longitude)

  • When an acceptable new value is entered, the additional description (e.g. 14 degrees, 25.4 minutes South) is updated to reflect the new value. Note that this description is not editable directly.

  • Latitude and Longitude are not available when bulk editing. The label is greyed out and content (and additional description) is blank.

 

UTC Offset:

  • The dropdown list has values from -12 to 12.

  • The default value is 0:0 for each new location.

  • When bulk editing, the label is greyed out and content is blank.

 

DST Details:

The Date and Time fields are consistent with similar fields on the User Interface (UI). In particular, the time field allows both keyboard editing and increment/decrement of minutes and hours.


When adding or editing a single location, the first dropdown offers the following choices:

  • None

  • DST Switch ON

  • DST Switch OFF

  • The default value is None for each new location.

 

Bulk editing

The first dropdown offers the following choices:

  • Do not set

  • None

  • DST Switch ON

  • DST Switch OFF.


When bulk editing, for each separate DST record (e.g. 2013 FIRST), if all the selected locations currently have the same value, the values are populated. However if all are blank, the first dropdown will default to None; otherwise the first drop-down defaults to Do not set and the remaining date/time boxes are blank. Whenever the first drop-down is set to None, the remaining date/time boxes are blank.


When the first drop-down is set to DST Switch ON or DST Switch OFF, the year values will be available as follows:

  • For the 2 fixed years, Year will be set to that year, and cannot be changed.

  • For the 2 records for before the current year, Year will be initialized to the previous year, but can be changed to any value between 2000 and that year (e.g. between 2000 and 2012).


Whenever the first drop-down is changed to DST Switch ON or DST Switch OFF, from either None or Do not set, the date/time fields will initialize as follows:

  • Month is blank and will show a dropdown (you must select a month)

  • Day is blank and will show a dropdown (you must select a day)

  • Year is set (or initialized) to the appropriate year (as defined above)

  • Time will initialize to 02:00.


Note that if DST Switch ON is changed to DST Switch OFF, or vice versa, the date/time fields will not change. The system will refuse to save the changes (with an appropriate error message) if the DST fields do not conform exactly to the DST Field Validation. In the case of a bulk edit, the validity of the new values will be enforced separately for each location using existing values for any records where Do not set is selected.

 

Editing DST Before the Current Year

This section describes how the system processes changes to saved  locations if either of the 2 DST values before the current year have been edited. In the case of a bulk edit, this functionality is applied separately to each individual location.


If the new values include 2 actual DST changes before the current year (i.e. SECOND LAST and LAST are both non-empty),: 

  • The 2 new values become the last 2 changes in the database before the current year.

  • DST changes already present in the database before the current year will be deleted if they are either:

    • equal to or after the date/time of the new SECOND LAST change

    • in the same year as BOTH the new values (i.e. the 2 new values are both in the same year, and so is the pre-existing value)

    • earlier in the same year as the new SECOND LAST change and of the same DST switch type (ON or OFF).


DST changes already present in the database before the current year that are not deleted based on the above criteria remain unchanged. This allows for older values (which could sometimes affect old runs) to remain in the database.


For Example

Location ABC has the following DST changes already in the database:

  • 2010-03-10 02:00 switch ON

  • 2010-10-05 02:00 switch OFF

  • 2011-03-09 02:00 switch ON

  • 2011-10-04 02:00 switch OFF

  • 2012-03-01 02:00 switch ON

  • 2012-09-01 02:00 switch OFF.


2013 is now the current year, location ABC is being edited, and the new values for BEFORE 2013 are as follows:

  • 2012-03-08 02:00 switch ON (SECOND LAST)

  • 2012-10-03 02:00 switch OFF (LAST).


Of the 6 previous records:

  • 2012-09-01 02:00 switch OFF is removed because it is after the new SECOND LAST value (2012-03-08 02:00)

  • 2012-03-01 02:00 switch ON is removed because it is in the same year as BOTH the new changes.

  • The previous 4 records remain in the system.


Therefore, the new DST records (before 2013) for location ABC would be:

  • 2010-03-10 02:00 switch ON

  • 2010-10-05 02:00 switch OFF

  • 2011-03-09 02:00 switch ON

  • 2011-10-04 02:00 switch OFF

  • 2012-03-08 02:00 switch ON

  • 2012-10-03 02:00 switch OFF .


If the new values include only 1 actual DST change before the anchor year (i.e. SECOND LAST is empty and LAST is non-empty), then:

  • The value provided will become the last change in the database before the anchor year

  • All other changes previously in the database before the current year will be removed.


For Example

Location ABC has the following DST changes already in the database:

  • 2010-03-10 02:00 switch ON

  • 2010-10-05 02:00 switch OFF

  • 2011-03-09 02:00 switch ON

  • 2011-10-04 02:00 switch OFF

  • 2012-03-01 02:00 switch ON

  • 2012-09-01 02:00 switch OFF


2013 is now the current year, location ABC is being edited, and the new values for BEFORE 2013 are as follows:

  • blank (SECOND LAST)

  • 2012-10-03 02:00 switch OFF (LAST).


All old records are removed, therefore the new DST records (before 2013) for location ABC would be:

  • 2012-10-03 02:00 switch OFF 


If the new values include no DST changes before the current year (i.e. SECOND LAST and LAST are both empty), then all changes previously in the database before the current year will be removed.


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.