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.

INC-175762 · Issue 669398

BulkProcess harness deprecated in favor of BulkProcessing

Resolved in Pega Version 8.7

The harness pzBulkProcess has been marked as deprecated. In place of this, implement the new Bulk Action functionality available using the harness pzBulkProcessing.

INC-163154 · Issue 638100

Code updated for bulk actions buttons

Resolved in Pega Version 8.7

After upgrade, hovering over the "Filter case" button in pzBullkUpdate and the "Create" and "Clear" buttons in pzBulkAddActions caused them to disappear. The warning "This button generates markup that was used to support the older browsers. It is recommended that you update it to the newer markup" was shown, and an update code button appeared. Some custom rules exhibited the same behavior initially, but worked as expected after updating the code and saving them. This has been resolved by updating the buttons in pzBulkUpdate and pzAddBulkActions with the latest UI technologies used for button control codes.

INC-173505 · Issue 657024

Error message updated for data page with REDUX

Resolved in Pega Version 8.7

A WrongModeException was generated when a runtime activity was trying to access a missing property in a data page with REDUX enabled. To clarify the issue, the error has been modified to be a MissingPropertyException. In addition, property information for a page group property was inferred on the top level page when it should have been inferred on the embedded page. This has been changed to infer the correct property information for mode-based processing to work as expected.

INC-197112 · Issue 689260

Corrected unnecessary Severe Warnings for MSGraph account

Resolved in Pega Version 8.7

After configuring an email account with MSGraph settings and saving the the email account instance, three unneeded severe guardrail warnings were generated related to using D_pxGetApplicationSettingValue instead of a constant value. This has been resolved.

INC-191033 · Issue 684370

Security updated for viewing data tables

Resolved in Pega Version 8.7

In order to improve security related to viewing data table instances, the privilege pxListClassRecords has been created in @baseclass and added to the "may start" activity ListEditor. Please add the privilege pxListClassRecords to access groups using ListEditor.

INC-187750 · Issue 675635

Error message removed for adding a new datatype to a branch

Resolved in Pega Version 8.7

Clicking 'add data type' for an application when no unlocked rulesets were available resulted in the error message "No unlocked Rulesets/Versions found that are valid for this record. Unlock at least one Ruleset/Version that can contain records of this type.". However, it was possible to create a data type by choosing branch. Investigation showed this message was added by the activity pzLoadTypeToBeAdded and is not needed: it has been removed from the step that appended the message when validating on click of submit.

INC-175672 · Issue 655809

ServicePackage thread handling improvements

Resolved in Pega Version 8.7

Work recently done to improve the release of requestor pool threads for the ServicePackage has been further enhanced by adding an explicit status notification to the thread waiting for Data Pages to be loaded in background and added support for the use case of a missing object handler.

INC-131938 · Issue 598477

Locking and classmap improvements

Resolved in Pega Version 8.5.2

Threads were getting stuck inside classMap and tableInformationMap, causing nodes to go down. This was traced to issues with classmap performance and locking, and has been resolved by replacing the lock library with a newer version and refactoring the tableInformationMapImpl class to use a concurrent hashmap instead.

INC-191673 · Issue 679945

"Keep file open" updated

Resolved in Pega Version 8.7

When "keep file open" was checked, Connect-File was failing with a java.io.IOException: Stream Closed error if called more than once. When "keep file open" is checked, the very first Connect-File call saves the handle to the OutputFileStreamWrapper of the requestor page. Any subsequent Connect-File calls will access this saved OutputFileStream but the stream is already closed, resulting in the exception. To resolve this, the try-with-resources statement that closed the OutputStream has been removed.

INC-194594 · Issue 684714

Parameter handling updated for cloned environment

Resolved in Pega Version 8.7

The Editable data page parameters were not getting set in a cloned environment. This has been resolved by adding code to detect the use case ('append and map to action' with 'a new page' relation) and let it fallback to legacy code generation.

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