Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Date control not displaying in correct format after upgrade

SA-40350

Summary



After Pega 7.2.2 upgrade Read only date controls are not displayed in the correct format.

They are displayed in the format "20170518T130317.738 GMT" instead of "05/18/2017 01:03 PM" wherever "Control Inherited from Property" is used for Pega defined properties(px, py, pz proeprties).

User observed that the Pega defined dateTime properties have an updated UI control defined for them in Pega 7.2.2 ("pxDateTime" has been given as UI control in 7.2.2 whereas "DateTime-CalendarHarness" was the UI control in 7.1.1).

When user change "pxDateTime" UI Control of the property back to "DateTime-CalendarHarness"(by Private edit) the date is getting displayed properlyin correct format. Issue is only with the read-only format.


Error Messages



Not Applicable


Steps to Reproduce



1.Inherit control from property for a default property ex pySLADeadline.
2.Make the property read only.
3.Display the value of the property In UI.
4.Observe that the value displayed in "20170518T130317.738 GMT" format instead of "05/18/2017 01:03 PM" format.


Root Cause



A defect in Pegasystems code or rules:

The section code is not generated properly when the application is upgraded to Pega 7.2.2.

Note: No Issue with the control.

Resolution



Perform the following local-change:

Recreate the section rule again to solve the issue


Suggest Edit

Published September 20, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us