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-D47414 · Issue 513077

"Use null if empty" checkbox honored for GetSelectValues

Resolved in Pega Version 8.2.5

When Report Definition rule uses parameters as a value for filter criteria, a moderate performance warning was generated: ''Some of your filters are using a parameter with the "Use null if empty" option NOT selected. Please ensure that you do pass the parameter. Otherwise, the filter will be dropped entirely and execution of the report will result in very poor performance. If you do not want this behavior, select the "Use null if empty" option.'' When the "Use null if empty" checkbox was selected as suggested, the "Select values" button gave an empty list of possible values. This was traced to refactoring work done on Select Values which changed it to be backed by a Report Definition and Grid instead of a List View: the option was intended to be only temporarily disabled, but was missed. To correct this, the activity pzGetSelectValues has been updated to honor the checkbox and appropriately disable the "Use null if empty" option on the selected filter on the temporary copy of the report definition before it is executed.

SR-D48173 · Issue 515339

Resolved hang caused by cancelling report calculation

Resolved in Pega Version 8.2.5

When dragging a calculation into the report editor filter area, clicking X on the cancel modal that appeared caused a JavaScript exception to occur. This exception later prevented the ability to click the "done editing" button on the report. This has been resolved by modifying the pzpega_report_rafpopup.sj -- doRefresh API to pass the correct argument to reload the section API.

SR-D48442 · Issue 514046

ExportMode parameter sent to resolve duplicate rows in Export to Excel

Resolved in Pega Version 8.2.5

On performing Export to Excel for a report definition, duplicate rows were being exported for a column which had a TextAreaWithExpandSmall UI Control. Investigation showed that this control was looking for the exportmode parameter, which was not being sent. This parameter is now being sent.

SR-D49491 · Issue 515319

Updated sorting parameters order for better matching

Resolved in Pega Version 8.2.5

After choosing sorting for a column in a main summary report and then drilling down, a message appears indicating no records found even though there were results. The query showeds that the values for the 'where' clause were sent in the wrong order, causing a parameter mismatch. This has been resolved with an update to get the iterator before sorting so parameters match up correctly.

SR-D50805 · Issue 516098

Eligibility Builder Select Values search box is visible

Resolved in Pega Version 8.2.5

On the Offer rule, Eligibility tab in Eligibility Builder, when creating an eligibility row that used ' {property} equals {value}', on the Select values menu -> Existing values, there was no search box to navigate the list of property prompt values. This was traced to the select values gadget not using the "Prompt value" to be displayed as its label, and has been fixed.

SR-D32972 · Issue 513488

HTML entity handling added to URLObfuscation

Resolved in Pega Version 8.2.5

When URLObfuscation was enabled through the configuration settings, clicking on Operator -> Profile page generated an ArrayIndexOutOfBoundException. When obfuscation is used the decrypted string is parsed and the request map is populated, but HTML entities were not considered during this process. To resolve this, handling has been added for HTML entities and characters during obfuscation. Please note: URL Obfuscation is a legacy feature with many known limitations and it is no longer recommended that these settings be used.

SR-D37894 · Issue 505975

Query parameters will be cleared after redirection from authentication

Resolved in Pega Version 8.2.5

When using the /PRAuth Servlet, running a snapstart URL generated from a secondary application correctly executed SAML Authentication and Pega processing, but a second URL generated with different parameters ran with the parameters from the first request. The third and subsequent requests processed as expected with the parameters sent in with the request. Investigation showed that the previous parameters were picked due to the query string parameters not being cleared after redirection, and this issue has been resolved by updating the system so it will clear the parameters after issuing a redirect from the authentication policy engine.

SR-D38318 · Issue 515960

Data pages explicitly cleared after QP use

Resolved in Pega Version 8.2.5

The Util Node was showing as Offline in the Search Landing Page, and when Jobs were submitted for execution from other Nodes the message "Detected active run with unreachable nodes" was logged. The util node, configured as a backgroundprocessing node, was running QPs, the queue size for custom QPs is 500 messages /queue items per minute, but investigation showed the requestor level and thread level data pages corresponding to the QP activities were not being cleared after use. This led to high heap memory issues that made the node unreachable, and has been resolved by adding code to explicitly remove the data pages when processing has finished.

SR-D46536 · Issue 515793

Custom agent next run time will be rescheduled if the run failed

Resolved in Pega Version 8.2.5

If a customized agent that was set to run every day encountered an exception and failed to run, restarting the agent did not update it to the next run time, it still returned the passed trigger time as its next execution time. This has been resolved with an update that will reschedule the run if the next run time is in the past.

SR-D46681 · Issue 514433

SnapStart supports SAML2 Authentication

Resolved in Pega Version 8.2.5

When using an HTTP Post to SnapStart into Pega using PRCustom style or PRAuth style SAML authentication, the login was looping back to the login request. Investigation showed that the Pega ACS was posting data properly back to the RelayState URL, however the login activity was not getting the SAMLResponse and simply sent a SAML Login Request again. This has been fixed by updating reqContextURI in case of SAML2 Authentication service so pyActivity=value will be passed.

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