Skip to main content

UI Configurations

To see dates and times in your own time zone, switch between a 12-hour and a 24-hour clock, or change the number separators, set your preferences in UI Configurations. The settings are personal: each user has their own, and saving yours doesn't change what anyone else in the account sees.

To open UI Configurations, select Navigation (the grid icon in the OpenLM Platform header), then Platform Administration, then UI Configurations. The page opens as System Settings. :::

Set your time zone and formats​

To set your preferences:

  1. Open UI Configurations.

  2. Set each option:

    • Time zone: The time zone OpenLM converts times into before showing them to you. OpenLM applies daylight saving time automatically. The default is (UTC) Coordinated Universal Time.
    • Date Format: The order of day, month, and year, and whether times use a 12-hour or 24-hour clock. For more information, see Date formats.
    • Decimal Symbol: The character used as the decimal separator. The default is ..
    • Thousands Separator: The character used to group digits in large numbers. The default is ,.
    • Number of records per page: The starting page size for grids that use this setting. The default is 25.

  3. Select Save.

    Cancel puts back the values you last saved.

  4. Reload any OpenLM tab that was already open.

    A service reads your settings when it loads, so a tab opened before you saved keeps the old format.

Date formats​

Formats with hh use a 12-hour clock, and OpenLM services add AM or PM after the time. Formats with HH use a 24-hour clock. The default is yyyy-MM-dd hh:mm:ss.

The following table shows how each format displays 3:30 PM on July 29, 2026:

Date FormatDisplays 3:30 PM on July 29, 2026 as
dd/MM/yyyy hh:mm:ss29/07/2026 03:30:00 PM
MM/dd/yyyy hh:mm:ss07/29/2026 03:30:00 PM
yyyy-MM-dd hh:mm:ss2026-07-29 03:30:00 PM
dd/MM/yyyy HH:mm:ss29/07/2026 15:30:00
MM/dd/yyyy HH:mm:ss07/29/2026 15:30:00
yyyy-MM-dd HH:mm:ss2026-07-29 15:30:00

If you export reports to CSV, use a 24-hour format. For more information, see CSV times have no AM or PM.

Walkthrough​

To watch the steps, play the following walkthrough:

Open demo in a new tab

Where your settings apply​

Your settings don't apply everywhere, because some screens always use one fixed time zone. Before you change a setting that seems to be ignored, check where the date appears:

  • Your settings apply: Grids and date filters in services such as Usage, Denials, Licenses, License Access Control, Process Manager, and Agents Hub, and the CSV exports from Process Sessions and Touch Point Event Sessions.
  • Always UTC: The Reporting Dashboard, on every tab. Its times aren't converted to your time zone. A few scheduling settings also work in UTC, such as Bucket Duration in Process Manager and Shutdown Time UTC (hh:mm) in the Agents Hub agent configuration.
  • A separate time zone: The Personal Dashboard has its own Time zone in its header user menu. Your browser saves that choice. It starts at the browser's time zone, and UI Configurations doesn't change it. The Personal Dashboard always shows dates as MM/dd/yyyy with a 12-hour clock.
  • Set per request: The Reporting Data API formats CSV files with the userConfigurations sent in each request, not with your saved settings.

Fix dates and times that look wrong​

The following sections list common date and time problems and their fixes.

Why are dates in the wrong order, or the clock 12-hour instead of 24-hour?​

Change Date Format, select Save, and reload the app. Day-first formats start with dd, month-first formats with MM, and year-first formats with yyyy. Formats with HH use a 24-hour clock.

Why is every time off by the same number of hours?​

Your Time zone is the default, UTC, or set to a different zone. Each user has their own settings, so seeing correct times on a colleague's screen doesn't mean yours are set. Set your time zone, select Save, and reload any open OpenLM tabs.

Why don't Reporting Dashboard times match the other services?​

The Reporting Dashboard shows UTC, and the other services show your time zone, so the same session can show a different time in each. Daily figures in the dashboard are counted in UTC days, so activity near midnight can fall on a different day than it does in the other services. Convert to UTC before you compare the two.

Why is usage from one license server shifted by whole hours, or why are sessions missing?​

If times from one license server are off for every user, and other servers look right, check that license server's time zone. OpenLM uses the license server's Time Zone to convert the times its license manager reports into UTC. If that zone is wrong, usage and denials shift by the difference, and sessions that appear to start in the future can be dropped.

For a server added through the Broker, the Time Zone is copied from the Broker host's time zone when you approve the server. You can't edit it in OpenLM Platform, and a later change to the host's time zone isn't applied to servers you already approved.

To check and correct the time zone:

  1. Compare the Time Zone of the server on the Type tab with the Time Zone column of the Broker. Broker Hub shows the time zone of the host.
  2. If the Broker host's time zone or clock is wrong, correct it on the host before you approve any more servers from that Broker.
  3. If a server you already approved has the wrong Time Zone, contact OpenLM Support at support@openlm.com.

For more information, see License Servers and Broker Hub.

For license managers that the Broker reads from log files, the Broker log can also show a Likely timezone mismatch warning that names the host, port, and vendor.

Why are dates garbled or sessions missing for DSLS, Zoo, Tebis, Houdini, or SIMATIC?​

These license managers print dates in a regional format, and the Broker needs to know which one. To set the format:

  1. In the Broker UI, open the license manager.
  2. On the Settings tab, set Date format and Date language to match the output of the license manager.
  3. Select Check date format on file.

If the format doesn't match, OpenLM can't read the dates and that usage isn't recorded, or the day and month can be swapped. For more information, see Settings tab.

Why do CSV times have no AM or PM?​

CSV exports in a 12-hour (hh) format don't mark AM or PM, so 03:30:00 can mean either. Select a 24-hour (HH) Date Format before you export. In a Reporting Data API request, send an HH format in userConfigurations.

What if the dates are still wrong?​

Contact OpenLM Support at support@openlm.com with the following information:

  • The app and screen where the date appears.
  • Your Time zone and Date Format settings.
  • The license server, if the times come from one server.
  • A sample row that shows the value you see and the value you expect.
Last updated on by Maria Gilca

The documentation team might draft this page using a large language model. A technical writer reviews every page and verifies it against the product before publishing it. A human makes the final decision.