Pega DateTime in BST/GMT

User Experience
, , , , ,
1

Hi,

Greetings. Hope you are well! I am on Pega 23.1.3 and have an issue with a DateTime control in a section, a section is reused one using a readonly data page where the date times are shown in BST which is correct, same section is being reused in a local action via an editable data page, here the date times are shown as GMT, there is no change to control in section except that it was readonly in one place (where times are in BST).

Can anyone please let me know if i am missing anything?

Regards,

Bharat

2

@KOMARINA It seems that the DateTime control is displaying differently based on its context (read only vs editable). In Pega the DateTime value shown in the DateTime control can differ from the Timeline control when using locale settings. For instance a DateTime value displayed in British Summer Time (BST) may show as GMT in other contexts. This could be due to how the Moment JavaScript library handles time zones. You might want to ensure that the Pega date time formatter is being used consistently across both contexts to maintain the same display format. Additionally check if there are any specific configurations or settings in the editable data page that might affect the time zone display.

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

Troubleshooting DateTime issues

3

hi @KOMARINA,

  • Time Zone Settings:

    • When using a read-only data page, Pega likely defaults to the time zone of the user session (BST in your case).
    • For editable data pages, the behavior might differ, as Pega may use the server’s default time zone (GMT in your case) or rely on explicit configurations.

  • Control Configuration:

    • Ensure the DateTime control has consistent configurations in both cases. Look for any differences in the “Display As” or “Formatting” options.

  • Operator Time Zone:

    • Check the operator profile’s time zone. If the editable data page overrides the session time zone, it might cause this discrepancy.

  • Data Transformation/Mapping:

    • If the section uses transformations or mappings, the date-time format or time zone might change during processing.

  • Section Rendering Context:

    • The rendering context for the local action might interpret the date-time differently due to the editable state, as it uses additional layers of processing.