How data is inserted into the NuGenesis SDMS database - WKB200997

ENVIRONMENT

• NuGenesis 8 SDMS
• NuGenesis 9 SDMS

ANSWER

Any testing being done with changing timezones should include a reboot once a timezone is changed, because the old timezone information is been cached and will still being used by SDMS.

The behavior of which Date / Time / Timezone is covered at which step is fixed and there is no way to customize it within the application.

 

 

Printing UNIFY

Initiated print from Wordpad

10:32:17 On Tag Dialog (waited for a bit before clicking OK)

 

Web Vision
Date/Time of Print = 2014-07-31 10:32:17 Timezone = GMT -10

Date/Time of Print is the Date/Time that the print job was started (or when we became aware of it). It is Client (printing system) time.

 

Date/Time of Database Insertion = 2014-07-31 16:35:02 Timezone = GMT -4

Date/Time of Database Insertion is the Date/Time when the processing of the job is complete, and we insert it into the database. This is Application Server time.

Because waiting a while before clicking on the OK button on the Tag dialog, there is a few minutes difference between the start of the print and the database insertion. Depending on configuration / how busy a system is / print size etc... there could be quite a bit of time difference.

 

Audit Trail
Server Date/Time (UTC) = 2014-07-31 20:35:02

Server Date/Time (UTC) is the UTC date/time of the application server when the audit trail entry was created.

 

Client Date/Time = 2014-07-31 10:35:02 Client Timezone = GMT -10

Client Date/Time is the Client time when the audit trail entry was created, depending on how the connection is established to the database.

Is the printing Client using the RPC service from the webserver for connecting to the DB ->tthis resulted in "Client Timezone" of the Webserver.

Is on the printing Client even an Oracle Client installed, the Client PC is now using the local connection to the DB -> this resulted in "Client Timezone" of the Client PC.

 

The values for the audit trail are when the audit entry itself gets created and should be almost immediately after the insertion time.

 

eSignature History

 

eSigned on: date/time when the button <Authenticate> is clicked.  When signing through NuGenesis Preview, the date/time and time zone is pulled from the OS where Preview runs, which could be the user's client machine or a Citrix server.  When signing through WebVision this date/time and time zone will be pulled from the OS of the Web Server machine.

 

The eSignature history is pulled from the audit trail records for the selected report.  The fields in the history map to fields in the audit trail:

eSig field name = Audit Trail field name

eSigned By = Authenticated ID
Full Name = User's Full Name
Employee ID = Employee ID
eSigned From = Machine Name + NT Domain Name + OS User Name
eSigned on = Client Date/Time + Client Timezone
Server Date/Time = Server Date/Time (UTC)  !!! translated to the machine's time zone!!!!  Viewing the eSig history in Preview you get the UTC timestamp converted to the machine's timezone.
Authorization Mode = Authentication Method
Reason Code = ESig Reason
Placed Comment = ESig Comment

So, the Server Date/Time is recorded by the server as a UTC timestamp, but the client machine translates it to the client's time zone when displaying it.  This can result in different time zone offsets displayed for the timestamp, because the conversion uses the local GMT offset at the time of the conversion, not the GMT offset at the time of the event, and the GMT offset for the physical location changes through the year due to Summer/Daylight Savings time.

 

Server Date/Time: The date/time and timezone are pulled from the OS of the NuGenesis RPC service machine at the time that the button is clicked.

 

Citrix environment

In case of an Citrix environment having different timezones of Citrix server and client, an issue with a mixture of Server Date/Time and Client Timezone has been observed. Below is a statement with recommendations to ensure that SDMS is working as designed to meet compliance requirements even in a Citrix environment.

File Capture

Date/Time of Capture = 2014-07-31 10:32:17 Timezone = GMT -10

Date/Time of Print is the Date/Time that the File was finished being copied to TE_TEMP on the File Capture Server. It is the File Capture Server time not the client time were the files were picked up from.

 

Date/Time of Database Insertion = 2014-07-31 16:35:02 Timezone = GMT -4

Date/Time of Database Insertion is the Date/Time when the processing of the job is complete, and we insert it into the database. This is the Database Server time.

There could be a delay between the finish of the files being copied into TE_TEMP and the start of the database insertion. Depending on configuration / how busy a system is / size of the files etc... there could be quite a bit of time difference.

 

ADDITIONAL INFORMATION