I have an issue in the notification reception time which still in GMT time instead of the operator time zone (not the time in the content of notification, I mean the reception time/ we are using OOTB send notification utility in a flow to send this notif). Exemple: I am supposed to receive a notification right now so instead of displaying below the notif 2:30pm it displayed 1:30pm.
The localisation of the operator is well configured, the ignore localisation is well uncheck, etc.
Could anyone have an explication why the I receive the notification in GMT time instead of my local time zone.
checking the datetime control you are using if the time zone source is set to Operator’s time zone rather than server.
Check for hardcoded GMT in the notification payload, since you are using ootb utility. if the time is a custom text field, then it won’t be automatically converted by the UI, you have to handle the conversion into desired time zone.
look for DisableTimeZoneConversion DSS in your system, if it is set to true pega will ignore operators’ localization and show in GMT at all time.
The OOTB Send Notification utility works through the Notification Rule + pxNotify engine, which sends the notification payload with server-side timestamps.
The reception timestamp shown in the notification panel is NOT the timestamp you provide inside the Notification rule; it is generated by the Notification Service, and that service always stores timestamps in GMT in the pyCreatedDateTime or pxTimeStamp fields.
Under normal circumstances, the UI layer automatically converts that GMT timestamp into the operator’s local time zone. If you’re seeing GMT instead of local time, it implies the UI is rendering a raw DateTime property that is already a STRING (text), not a DateTime type.
Fix: Ensure the UI renders the timestamp using a DateTime control bound to the raw DateTime value from pxNotify Specifically: Use .pxTimeStamp or .pyCreatedDateTime (unmodified). Do NOT format or convert it to text.