

For example, a workspace with the following time zones will throw an error in the ‘View Status’ script even though they have different pre-pended values: Native time zones with the same name should not be set up in a workspace.If you are not a system admin, we recommend you do not run these scripts.

These scripts should only be run by a system admin.The solution supports the following functionality: Relativity script that runs at the workspace level.Relativity script that runs at the environment level.This solution consists of the following components: The application will not work unless you are on the most recent version of the application that works with your instance.
#Baseelements time zone offset upgrade
Note: After upgrading your Relativity instance, upgrade the Native Time Zone Offset application to the latest version of the application.
#Baseelements time zone offset download
This page contains the following sections:Ĭlick on the latest version of the application that works with your Relativity instance to download the application from the Relativity Community: The solution also sets the single object Time Zone field on the document object to be used for Imaging Profiles. This solution takes a configurable date field value and time zone and updates each newly loaded document’s Relativity Native Time Zone Offset field to account for daylight savings time. Therefore, it's important that you review and adjust the UTC accordingly to avoid incorrect time designations on documents you intend to produce, as this could lead to inaccurate productions.

This field also controls the date and time displayed on redacted and annotated images. So you will have to re-convert documents if documents have been previously viewed. It doesn't modify the actual metadata fields associated with these values.
