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-D11605 · Issue 485661

:JAWS correctly reads heading for Report browser/viewer

Resolved in Pega Version 8.2.3

JAWS 18 was not reading the titles in the report browser and report viewer as "heading level 1" as it should. For the Report Browser, JAWS was reading the title as "<title> - heading level 2", and for the Report Viewer, JAWS read the report title as "<title> - frame". This has been corrected by adding the appropriate aria tags to pzGetStyledLocalizedText.

SR-D1270 · Issue 488260

DB table mapping will check for existing properties before creating them

Resolved in Pega Version 8.2.3

Using the Database table class mapping tool to map an external database table to a class and create properties according to columns in the table was resulting in the property being created as 'not available' and not case sensitive if the property to be created while mapping was already present in the inheritance hierarchy. This led to an error caused by the property validation failing in the validateReportDesignTab activity. Previously the database table mapping tool did not check to see whether the properties to be created existed already in the parent class hierarchy. With this update, the system will check before allowing the mapping, and if the properties exist in the hierarchy already they will not be populated.

SR-D13388 · Issue 485169

Handling added for minor case creation errors

Resolved in Pega Version 8.2.3

When creating a case, if any step status failed due to a non-critical reason which did not impact case creation (for example, a mandatory parameter was missing from the data page), that failure state was propagated to SaveNew and ultimately to the case creation API. As a result of this failure report, no case ID information would be reported back to the requestor even though the case was created, and the API responded with status 500 - internal service error. This has been resolved by removing the StepStatusFail check from pzCreateCaseInternal so that non-breaking errors will not result in a 500 error, and a check has been added for page messages in svcAddWorkObject and svcPerformFlowAction so that validation messages are returned.

SR-D13450 · Issue 488137

Corrected Query logging level for Populate_UsepxRequiredSkillsCount

Resolved in Pega Version 8.2.3

A Query was being logged with Logging level of Error in pzPopulate_UsepxRequiredSkillsCount. This has been corrected.

SR-D13514 · Issue 489432

Data-test-id handling updated to resolve testing issue with custom controls

Resolved in Pega Version 8.2.3

After configuring a custom control, the control did not render as expected when trying to capture the scenario testing. Investigation showed that in readonly mode, two spans were wrapped with same data-test-id when formatType is number. This caused a ‘no unique selector’ issue with scenario tests. To resolve this, pzpega_ui_template_displayText.js has been updated to not include data-test-id on outer span when formatType is number.

SR-D13569 · Issue 491715

Additional parameter format added for multiselect controls

Resolved in Pega Version 8.2.3

Attempting to pass a parameter like "Value1", "Value2" to a data page used for the MultiSelect Control was not working even though the same format worked for autocomplete control. This was an issue where the flow of fetching the data differed between the two controls, and support for this parameter format has now been added for multiselect controls.

SR-D13880 · Issue 483332

Support added for using WorkPage class for FieldValue evaluation

Resolved in Pega Version 8.2.3

The Instructions provided under the Assignment details section of an assignment shape were not evaluating the FieldValue for the work object's audit history entries unless the field value was defined only at @baseclass. This was due to WorkPage class not being considered while evaluating a FieldValue, and has been resolved by modifying the InstructionsLookup control to use work class instead of the hard coded @baseclass.

SR-D14159 · Issue 493082

Toggle added for displaying exception stack trace

Resolved in Pega Version 8.2.3

When text like "%25" was added to the login URL, the full exception stack was displayed on the screen. To resolve this, when the prconfig 'initialization/displayexceptiontraceback' is set to false (default value), the system will render the status.jsp instead of error.jsp and will not populate any sensitive data in the request object. If its set to true, the system will fall back to the old approach which renders error.jsp and emits the stacktrace.

SR-D14161 · Issue 490594

XSS protection added to decryptURLString

Resolved in Pega Version 8.2.3

In order to secure against Cross-Site Scripting attacks, decryptURLString will return a blank string instead of plain text if it is not given valid encrypted text.

SR-D14521 · Issue 486528

Added support for sorting by field value instead of localized value

Resolved in Pega Version 8.2.3

In a datapage-sourced dropdown with 'group by functionality' enabled in ascending order, the values were being sorted according to their localized value and not their field value. This was a difference between templatized and non-templatized handling, and has been resolved by adding the ability to sort the group label by field value in the templatized UI.

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