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-224487 · Issue 729466

Security test status message includes assignment

Resolved in Pega Version 8.8

After update, the error message generated during a security test returned Status OK 200 but without any content. This was traced to a skipped step in pzGetAssignmentActionDetails activity and has been corrected.

INC-225615 · Issue 725299

BAC updated for delegated circumstanced decision table rule

Resolved in Pega Version 8.8

An unregistered request error was encountered while launching the DelegatedRulesPage harness when pyBlockUnregisteredRequests >=1. This was traced to a delegated circumstanced decision table rule which caused a request error for the @baseclass.pzLookupCircumList activity, and has been resolved by updating the BAC handling for this activity.

INC-227714 · Issue 730395

Empty check added to OpenRuleAdvanced

Resolved in Pega Version 8.8

A blank screen was displayed when attempting to open a requirement set rule in Dev Studio. This was a missed use case while updating the OpenRuleAdvanced control to handle BAC compatibility, and has been resolved by adding an empty check in addition to the existing null check along with an 'if' condition to check for pyActivity input.

INC-227819 · Issue 735349

Improved browser compatibility for ContentDisposition header

Resolved in Pega Version 8.8

When files were downloaded from a Sharepoint repository by clicking on the link, the filename was appended by a unique case instance ID or a sequence number to avoid duplicates. This caused a workflow disruption due to the reupload considering the file to be new rather than updated. This was traced to an issue with the usage of the ContentDisposition header which should have set the default file name: as created, the method was not compatible with Google Chrome on Microsoft Windows and was ignored. This has been corrected by updating the ContentDisposition header to set the default file name correctly when using supported browsers.

INC-229440 · Issue 734024

isRulesetLocked updated for efficiency

Resolved in Pega Version 8.8

When trying to access some access roles, the error "The number of database bytes input for this interaction has exceeded the ERROR level for Requestor" was generated. Investigation showed there were many read-BLOB events being triggered by the when rule pzRuleInLockedRuleSet. To address this, isrulesetlocked has been modified to not open every version of a ruleset, but instead perform a simple count and check if the ruleset exists.

INC-233264 · Issue 743670

Rule updated to "Refactor Copy Move Merge"

Resolved in Pega Version 8.8

The Pega-RulesRefactoring:08-01-01 agent rule "Refactor Copy/Move/Merge" has been updated to remove the '/' character as it was interfering with the agent name validation.

INC-183485 · Issue 699787

ClientCache performance optimization

Resolved in Pega Version 8.8

In order to improve performance for the mobile app, updates have been made to optimize the ClientCache list interations.

INC-190053 · Issue 680232

Mobile attachment count corrected

Resolved in Pega Version 8.8

Parametrized data pages were not being populated as expected, causing an incorrect attachment count when opening a case in Mobile. This has been corrected.

INC-192649 · Issue 706132

Basereference context available for attach content control

Resolved in Pega Version 8.8

An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.

INC-198193 · Issue 723626

Error correctly shows for each attempt to upload an oversize file

Resolved in Pega Version 8.8

The error message indicating an uploaded file exceeded the permitted file size was only shown on the first try on Android. Subsequent attempts to upload the same oversize file did not generate any error. This was due to a persisting value, and has been resolved by explicitly clearing the input value for the mobile browser upload.

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