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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-C84643 · Issue 423856

Logs now support RandomAccessFileAppender

Resolved in Pega Version 8.1.4

Support has been added to the LogFileDownload and LogViewer HTML final rules for using RandomAccessFileAppender. This is in addition to the existing support for RollingRandomAccessFileAppender and RollingFileAppender.

SR-C74642 · Issue 424007

Data page reference properties will not be resolved if hidden

Resolved in Pega Version 8.1.4

In order to improve code efficiency, in conditions where a text input field configured with a 'When' visibility condition references a property which is present in a data page, the system will skip the process of resolving the property name if the 'When' rule is evaluated as false.

SR-C81410 · Issue 422138

Radiobutton aria-label enhanced to retrieve localized field value

Resolved in Pega Version 8.1.4

Localization code has been added to the pzpega_ui_template_radiogroup file to support using RadioButton aria-labels for Field value.

INC-200247 · Issue 701954

WorkAttachmentIcon activity correctly registered

Resolved in Pega Version 8.6.4

The pyWorkAttachmentIcon control used to download attachments was generating a SECU0019 warning. This was traced to pzAppStorageOkToAttachFile not being correctly registered, and has been resolved.

INC-210526 · Issue 705640

Mobile supports icons for file attachment

Resolved in Pega Version 8.6.4

Attaching a file to a case in a mobile browser generated a script error popup. This has been resolved with code to support using icons to attach files on mobile.

INC-140725 · Issue 597474

Custom question parameters visible in survey

Resolved in Pega Version 8.5.2

When opening an individual question in the custom question section of a survey, the parameters passed were visible in the Answer tab but not when clicking on the getParams link in the right-side panel. This has been resolved by updating the pzSetRuleAndPropValuesForQuestion activity to copy section params from the question rule and call GetSectionParamsToPrompt to get latest parameters data.

INC-148115 · Issue 605421

Autocomplete results list position scrolls inside a table

Resolved in Pega Version 8.5.2

Given a row editable table with a fixed height and freeze grid header, when autocomplete was included in a row of a table and the down-arrow was pressed to get the list of options in dropdown, this drop-down popup was not moving along with the row during scrolling. This was due to scroll handler not being triggered for popover when inside a hierarchical table, and has been resolved.

INC-209906 · Issue 704866

AddMessage function shows error on UI

Resolved in Pega Version 8.6.4

After updating from Pega 8.1 to 8.6, an addmessage function which previously displayed an edit validate rule error message was not working. This was an issue with textinput inside a grid, and has been resolved by adding a style to input text when it has a symbol left aligned and giving the error icon a z-index to show the message when the symbol is configured.

INC-140110 · Issue 600398

Large filter values accepted in Report Definition edit

Resolved in Pega Version 8.5.2

Report definition edit filter values were not accepting large comma separated values properly. This has been resolved by modifying the logic in RRFilters_Logic to use ReportFilter.getReportFilters.

INC-134808 · Issue 590711

Property check handling updated for Ajax requestor

Resolved in Pega Version 8.5.2

SECU0001 alerts were seen when submitting a case in the interaction portal. Logging indicated the errors were related to the 'pxRequestor.pyLatitude' and 'pxRequestor.pyLongitude' properties which are included in an Ajax request when they exist in the DOM and the 'pyGeolocationTrackingIsEnabled' when rule is true. The error was traced to a condition where a new thread request results in an unexpected property check that encounters a clipboard which doesn't have any pages created for that thread. To resolve this, the 'pxRequestor.pyLatitude' and 'pxRequestor.pyLongitude' properties have been added to an allow list to handle the unexpected properties check.

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