Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-A18716 · Issue 234856

Corrected Hotfix Manager mismatch between 7.2 versions

Resolved in Pega Version 7.2.1

The version of 7.2 used in the Hotfix Catalog was different from the version used in Hotfix Manager when installing DLs. An update to the HM code was made to correct this mismatch.

SR-A18722 · Issue 240874

Resolved alert for PYLOADMYCASESTREE

Resolved in Pega Version 7.2.1

While trying to invoke the out-of-the-box activity pyLoadMyCasesTree, a Pega0050 alert was triggered and logged. The function is failing to copy the items to Code-Pega-List from the pxResults due to the class of treePage which contains all the cases that needs to be displayed in the Gadgets. The tree page has been changed to @baseclass to resolve this issue.

SR-A18766 · Issue 235529

Documentation updated to reflect MaxRecords blank value = 0

Resolved in Pega Version 7.2.1

The developer help for the Max Records field on the Schedule tab of the Agents rule form states "If this field is blank, the default value is 50.". In actuality, a blank value in Max Records behaves the same as a value of 0, i.e. "process all entries in its queue before sleeping". This was a documentation error, and the help topic in question has been updated to reflect the actual results of the blank field.

SR-A18787 · Issue 240329

Busy icon shows properly when clicking Save/Refresh

Resolved in Pega Version 7.2.1

The Busy indicator has been updated to ensure it appears as expected after clicking the Save/Refresh button of any harness.

SR-A18813 · Issue 236196

Support added for auto-generated numeric IDENTITY columns in RD

Resolved in Pega Version 7.2.1

Because IDENTITY auto-generated columns were not supported , RD did not identity the column of type numeric() IDENTITY and generated an error when accessing a table with NUMERIC column types in SQL Server 2012. Numeric() TYPE was already supported for generation in RD, and an SQL connector has been added to handle tables with numeric() IDENTITY as well.

SR-A18899 · Issue 236697

Operator ID screen messages localized

Resolved in Pega Version 7.2.1

Localization has been added for error messages generated in the Operator ID Screen.

SR-A18902 · Issue 237052

Updated tab generation for failed 'when'

Resolved in Pega Version 7.2.1

When visible 'whens' were configured on accordion, the content was not properly displayed below the header if the 'when' condition was false. This was caused by an error in the generation of defaultTab based on visible 'when's, and the GenerateTabbedSectionLayout RUF has been updated.

SR-A18905 · Issue 233955

OrgName error resolved for MobileOffline:Obj-Open-By-Handle

Resolved in Pega Version 7.2.1

If Obj-Open-By-Handle was configured on the Org Name link in MobileOffline for the master details of a Contact Work Object, clicking on the link generated an "Empty Work Item Handle" error despite the OrganizationID(Handle) being present on the data page. This was an error in the actions array for the "runScript" API, and has been fixed.

SR-A18905 · Issue 235333

OrgName error resolved for MobileOffline:Obj-Open-By-Handle

Resolved in Pega Version 7.2.1

If Obj-Open-By-Handle was configured on the Org Name link in MobileOffline for the master details of a Contact Work Object, clicking on the link generated an "Empty Work Item Handle" error despite the OrganizationID(Handle) being present on the data page. This was an error in the actions array for the "runScript" API, and has been fixed.

SR-A18909 · Issue 235146

Strategy and data flow behavior more consistent

Resolved in Pega Version 7.2.1

Strategy execution via data flow was producing different results depending on how it was executed. This was caused by the use of different types of pages based on the execution method, and the code has been updated to produce more consistent behavior.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us