Time zone conversion for non‑system date fields
The Date Field Time Zone Conversion Enabled setting determines how the system interprets and stores non‑system date fields that users enter through the user interface (UI). This setting helps organizations control whether such dates should reflect the server time zone or be adjusted based on the end user’s local time zone. For more information, see Understanding system and non-system date fields .
When the Date Field Time Zone Conversion Enabled setting is enabled (true), OpenPages® performs time zone conversion for all
non‑system date fields except those that are set via public APIs (like in a helper):
- Date values entered by an end user are converted from the user’s local time zone to the server time zone before they are saved.
- When another user views the same record, OpenPages converts the saved date from the server time zone to the viewing user’s local time zone.
-
Note: Because OpenPages treats date‑only fields as occurring at 00:00 (midnight) during conversion, users in different time zones may see different calendar dates for the same field.
By default, the setting is disabled (false) and OpenPages does not perform any time zone conversion
for non‑system date fields:
- Dates are stored exactly as entered, directly in the server’s time zone.
- All users see the same date value, regardless of their individual time zones.
- Time zone differences do not affect how the date appears in the UI.
Remember: Notify users if you change this setting. Because there are no visual
indicators of the change, users might continue relying on the previous time zone configuration,
which can result in misinterpreted date and time values.
- Default: false