In our application we have defined a specific locale format through the option : Pega -> User Interface -> Localization Tools -> Locale Settings
But even after setting the locale to desired format, pega picks up the date format from the browser settings. If the locale setting is different from browser setting, then browser setting precedes. Is this the expected behaviour?
Is there any way we could stop the date format change from occurring? or Is this a product issue?
We have set our pega locale settings to en_AU.
But some users have their browser setting as en_US in (Google Chrome browser).
This conflict in locale settings causes the validations to fail when logged in from a browser which has en_US format.
If we have sections defined with DateTime control, then the Date time control in the editable format displays in en_US format rather than en_AU.
When user selects the date in their system, the date comes up as MM/dd/yyyy rather than dd/MM/yyyy.
Why pega is not picking up from the locale settings defined in the product? Why does it pick the browser settings?
I have the same issue but the operator id is already configured the locale as en_AU and i am checking the application from IST timezone.so in the date picker the date is not setting default to Australia's date when the date changes in AEDT.
ex: 23/11/2016 is today's date after 6:30 PM IST if we check the date picker it is still showing 23 as the selected date instead of 24.
This comment has been branched out as a new node and the new thread can be followed here
Posted: 5 years ago
Posted: 23 Nov 2016 11:34 EST
Lochana Durgada Vijayakumar (Lochan_DV)
Senior Manager, Knowledge Management