PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 04/25/2012 10:08 PM by  Rod Weir
Database changes for v12 - UTC date conversion - VERY IMPORTANT!
 0 Replies
AddThis - Bookmarking and Sharing Button
Sort:
You are not authorized to post a reply.
Author Messages
Rod Weir
HelpMaster development team
Helpdesk expert
Helpdesk expert
Posts:531
Points:947


--
04/25/2012 10:08 PM

    Background

    HelpMaster v12 and above supports multiple timezones when entering, updating or viewing any date/time data.  This is very useful if you use HelpMaster across different timezones.

    In order to support this functionality, HelpMaster needs to store all date data in the database as UTC (Universal coordinated time).  When the date data is displayed to the end user, it is converted and displayed in local time.  If the timezone for the date is different to the local time, HelpMaster will indicate this.

    For all versions of HelpMaster prior to v12, the date data that has been entered into HelpMaster by each person in each location will be in their local time.   The date data displayed to each person will also be this time.  This can be confusing and misleading if you do not realize where each entry originated from.  A person viewing a date that was entered in a different timezone may not realize this.

    This is the issue that v12 addresses.

    By storing all date data in a common date timezone such as UTC, the timezone information and time offset (including daylight savings time) can be used to display date data in local time and preserve the original timezone data.

    Database upgrade and conversion

    In order to use HelpMaster v12, you will need to upgrade your database.  Use the HelpMaster database and reports wizard to automatically do this.  All of your existing HelpMaster data will be upgraded and all date data will be converted to UTC - nothing is lost.

    However!  It is very important to run the Database and Reports Wizard on a computer that has its' date timezone (Windows timezone) set to the same timezone that the majority of your date data is entered in.  This will allow the conversion process to convert your existing date data into UTC and preserve the same ratio of timezone information.

    For example.

    Suppose you have people using HelpMaster in 3 different timezones.

    • Timezone 1 = Wellington, New Zealand (+12)
    • Timezone 2 = Sydney, Australia (+10)
    • Timezone 3 = Perth, Australia (+8)

    The majority of your data entry is from the Sydney office.  This means that users in NZ, or Perth will be accustomed to viewing the majority of date data that is not in their timezone.

    The HelpMaster database upgrade to v12 will update all date data, however by running the conversion on a machine running in the same timezone as the majority of your date data, you preserve this same ratio of timezone differences for existing data only.  The effect for existing data will be business as usual - that is, the same potential ambiguity will exist.

    All new date data entry in HelpMaster v12 will be stored as UTC with timezone encoding and this ambiguity will no longer exist.

    Make a database backup and test!

    As usual, it is highly recommended to make a backup of your existing HelpMaster database before performing the database upgrade.  It is also recommended to view your converted data for any issues before converting your live production HelpMaster database.

    Date display in HelpMaster v12

    Once your HelpMaster database has been converted, all date data entry will be encoded with the originating timezone and v12 will store this data in the database in UTC.  When this date data is displayed, it will be converted back to a local timezone and all ambiguity will be removed.  Each person using HelpMaster will be able to tell where and when the date was entered, regardless of where it was entered.

    Custom reports

    If you have created custom reports that pull data from your HelpMaster database, you will need to update these to account for the changes in the date fields.  Remeber, all date fields in the database will now be in UTC.  You will need to convert these to your preferred timezone.

    For information about updating Crystal Reports, please refer to this discussion thread.

    Getting help, have questions?

    Please post any questions, or issues you have about this here.

    Thank you,
    The HelpMaster development team

    HelpMaster development team
    Check out the HelpMaster roadmap
    You are not authorized to post a reply.


    November 2018 release now available by Rod Weir in Announcements with 0 replies A new release of HelpMaster is now available.  This release contains lots of fixes, performance tweaks, improved workflow capabilities, improved ...

    Quick Re-assign from an "Unassigned" skillgroup queue by Rod Weir in Using HelpMaster with 0 replies The upcoming November release of HelpMaster contains a small, but very handy new feature. When a job is assigned to the "Unassigned" queu...

    Job Templates get a new config option for web-based jobs by Rod Weir in Web interface, client self-service and remote access with 1 replies For the up-coming November release of HelpMaster, we've updated the Job Templates so that they can be configured as "Web Forms".  ...

    Maintenance release of HelpMaster, v17.22.5 is now available by Rod Weir in Announcements with 0 replies A new release of HelpMaster is now available.  This release delivers some exciting new workflow improvements, along with improved staff web porta...

    New employee on-boarding workflow using new workflow objects by Rod Weir in Using HelpMaster with 0 replies As the workflow capabilities of HelpMaster continue to improve, one of the things that we've been seeing from users of HelpMaster is building proc...

    RE: Job Templates get a new config option for web-based jobs by Rod Weir in Web interface, client self-service and remote access Just further to this topic....if using workflow to log a new job from a job that already contains control sets, and you are using the option to transf...

    November 2018 release now available by Rod Weir in Announcements A new release of HelpMaster is now available.  This release contains lots of fixes, performance tweaks, improved workflow capabilities, improved ...

    Quick Re-assign from an "Unassigned" skillgroup queue by Rod Weir in Using HelpMaster The upcoming November release of HelpMaster contains a small, but very handy new feature. When a job is assigned to the "Unassigned" queu...

    Job Templates get a new config option for web-based jobs by Rod Weir in Web interface, client self-service and remote access For the up-coming November release of HelpMaster, we've updated the Job Templates so that they can be configured as "Web Forms".  ...

    Maintenance release of HelpMaster, v17.22.5 is now available by Rod Weir in Announcements A new release of HelpMaster is now available.  This release delivers some exciting new workflow improvements, along with improved staff web porta...

    New employee on-boarding workflow using new workflow objects by Rod Weir in Using HelpMaster As the workflow capabilities of HelpMaster continue to improve, one of the things that we've been seeing from users of HelpMaster is building proc...

    Maintenance release of HelpMaster, v17.20.14 is now available by Rod Weir in Announcements A new release for v17 is now available.   This release fixes a number of issues for version 17 as well as new and enhanced features. &...

    Video settings on 4K monitors and/or high DPI settings by Rod Weir in Bugs!!! We've recently been getting bug reports of not being able to select items from drop-down boxes on the job screen (and others) when using high-res ...

    Faster entity search screens coming by Rod Weir in Using HelpMaster Next release of HelpMaster will feature faster entity search screens (clients, sites, assets, all templates etc).  We've re-factored a lot of...

    RE: Email Manager and Priority Manager services by Rod Weir in Bugs!!! Hi Josh, Thanks for reporting this and for assisting the dev team off-line to diagnose this issue. We've been working on the code and have foun...