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.

INC-185824 · Issue 676630

Corrected filtered column list sorting in Report Browser

Resolved in Pega Version 8.6.5

Sorting was not working in Report Browser for a column list when a filter category was selected. This has been resolved by modifying the pzReportListSort activity to set the correct parameters in step-1 and setting pzSetCategoryParam to retain the sortTitle parameter in step 1 with an added step -2 to call the pzReportListSort activity.

INC-205464 · Issue 721607

Performance improvements for KYC query

Resolved in Pega Version 8.6.5

The GetApplicationKYCTypes report definition was exceeding the default maximum elapsed time of 30 seconds, causing all cases which were part of the due diligence milestone in Client Lifecycle Management framework to be auto-completed. This has been resolved by improving the KYC Items query logic by removing mergeJoin and adding HashJoin Hints.

INC-210837 · Issue 707179

DateTime property correctly formatted in Report Editor

Resolved in Pega Version 8.6.5

When a list report was created via the Report Editor, dragging and dropping a date time property which was embedded inside another page and choosing the format as Date and Time resulted in the property taking pxTextInput instead of pxDateTime. This has been resolved by updating the pzMergeAutoGenForProp activity to get the correct class name for embedded page properties.

INC-211590 · Issue 711018

Auto-complete and calendar popover alignment corrected

Resolved in Pega Version 8.6.5

An issue with the container alignment of the auto-complete and calendar dropdown popovers has been resolved by removing styling in the pyReportEditorStyling .css which was causing the issue.

INC-212157 · Issue 721532

Report filter values correctly displayed

Resolved in Pega Version 8.6.5

The data page name was being displayed in report filters instead of actual values. This was traced to a missing step in the activity pzResolveCopyFilters which was needed to get the data page values in the report filter prompt, and has been resolved.

INC-215062 · Issue 722019

Removed ORDER BY clause duplication when using MSSQL

Resolved in Pega Version 8.6.5

After updating from Pega 8.4 to Pega 8.7, executing the query for the report definition generated the error "SQLServerException: Incorrect syntax near the keyword 'ORDER'." Investigation showed the ORDER BY clause was added to the Native SQL query from the standard dataflow background task and from the native SQL API as well when using an MSSQL database. This has been resolved by adding changes to restrict the order by clause if the SQL query has order by clause already for MSSQL.

INC-217475 · Issue 719043

Corrected duplication of records in Elasticsearch

Resolved in Pega Version 8.6.5

After creating a dedicated index for a data class, modifying any data record for external Data/Work classes caused duplicate documents to be created in Elasticsearch. This has been resolved by updating the Reindex _id field to use the pzInsKey value instead of an auto-generated string. Once this update is in place, re-index is required to remove already created duplicates from the index directory.

INC-217974 · Issue 715429

Handling added BIX extraction failure when called from custom activity

Resolved in Pega Version 8.6.5

After update, BIX extraction was failing but email from the schedulers indicated success. Investigation showed that when extract was called from a custom activity by calling pxExtractDataWithArgs, the stepStatusFail 'when' rule in the custom activity was not capturing all the exceptions specific to database extracts. This has been resolved by adding the necessary handling.

INC-201713 · Issue 700221

Resolved SSO logout error

Resolved in Pega Version 8.6.5

After configuring prconfig/initialization/Urlencryption/default -> true and prconfig/initialization/SubmitObfuscatedURL/default -> required, logging in to any portal using SSO resulted in a 400 error when trying to log out. This has been resolved by adding a call to the encryption Rule-Utility-Function while calling logoff activity from 'pzSingleLogoutServiceRedirectV2'.

INC-202702 · Issue 713726

Ruleset creation process updated to maintain thread scope

Resolved in Pega Version 8.6.5

On creating a ruleset, the system generated the error "There has been an issue. Please consult your system administrator." If browser cookies and site settings were cleared and the browser was relaunched before logging in and creating a ruleset, the issue did not occur. Investigation showed that the Application page was at the Requestor scope for some of the threads due to handling in the ruleset creation process that removed the Application page and recreated it in the default scope of the thread with the latest state. To resolve this, the process for deleting the Application page and recreating it on the Requestor page has been removed.

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