T65-2024 Timezones recorded as application server date/time rather than UTC

Portfolio

ENOVIA Quality and Regulatory Management

Program

ENOVIA QUMAS EQMS QA Manager

Trigram

PQQ

Media Set

AM_ENO_Q_EQMS.AllOS

Background

An issue has been identified in EQMS where timestamps are recorded using the application server's time instead of UTC. This problem was introduced in release R2022 (4.4 Patch 2) following the upgrade of our Hibernate component. The issue has been resolved in R2024 HotFix 1. QUMAS is also prepared to provide targeted PinPoint releases for clients impacted in their current release.
If required, QUMAS will collaborate with customers to provide database update scripts that adjust stored timestamps back to UTC instead of the application server timestamp. This process will require scripts to alter timestamp records. Customers should prepare internal documentation for a risk assessment and to explain the authorization of these changes. The key timestamps requiring updates are:

• Task: Created and completed timestamps
• Workflows: Start/finish timestamps, step entry/exit timestamps
• Process Instance: DateTime fields

The following timestamps will remain unchanged as they are Immutable timestamps: 

• Audit Trail: Event timestamp
• Electronic Signatures: Signature timestamp

Immutable timestamps: After the HotFix is applied, the Audit Trail and Electronic Signature timestamps created when the issue existed in the application will be displayed as UTC timestamp rather than in application server timezone. For example, an existing Audit Trail timestamp recorded at 10:00AM EST will display as 05:00AM and any new Audit Trail entries post HotFix will correctly display 10:00AM. Customers should note this in their internal documentation.

Solution

The defect PROC-9289 has been resolved in R2024 Hotfix 1. BIOVIA Support recommends contacting your Account Executive to discuss upgrading to the latest version.

Workaround

We recommend applying a PinPoint to the current installation to correct the issue with the storage and retrieval of timestamps. Additionally, we will provide scripts to update the impacted timestamps in the database, adjusting the stored values to UTC.

Workaround steps

1. Raise a service request on the 3DSupport app.
2. Request a PinPoint for the customer’s current level.
3. Provide a database dump to QUMAS for assessment and script preparation.
4. To implement the changes, the application will need to be stopped, scripts executed and the PinPoint applied.

We recommend that documentation is retained to explain this change

How to contact BIOVIA Support

If you have any questions, please contact BIOVIA Support.