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-207210 · Issue 703702

Empty check added to OpenRuleAdvanced

Resolved in Pega Version 8.7.1

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-182423 · Issue 691799

Pull to refresh disabled during case submission

Resolved in Pega Version 8.7.1

Triggering a refresh (swipe down) on mobile while the spinning loading indicator was shown resulted in the error 'This action is not allowed' instead of being able to view the case. This has been resolved by disabling pull to refresh when there is any background network activity in progress.

INC-183485 · Issue 692518

ClientCache performance optimization

Resolved in Pega Version 8.7.1

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

INC-195519 · Issue 698497

Support added for using CFW when Pega server is unavailable

Resolved in Pega Version 8.7.1

Data synchronization changes have been added to allow Client for Windows to work in offline mode without an AppCache manifest.

INC-199354 · Issue 696718

Corrected pulse comments rendering in mobile

Resolved in Pega Version 8.7.1

When using mobile, clicking the number on the Pulse comments section was not responding and conversations inside a comment were not visible. This has been resolved by updating pypega.social.js and pypega.social.css so the section renders correctly.

INC-199891 · Issue 695892

Updated handling for parametrized data pages on offline mobile app

Resolved in Pega Version 8.7.1

After update, the UI in the offline mobile app was showing .pyStandardValue and not the LookUpValue. This was caused by parametrized data pages not getting populated when used on UI components so the custom populator was not getting called, and has been corrected.

INC-206049 · Issue 703469

Resolved activity registration error for Scan Barcode/QR Code

Resolved in Pega Version 8.7.1

Attempting to add the action 'Scan Barcode/QR Code' to a button generated the warning "Unauthorized request detected : Unregistered request encountered with params pyActivity:pzRunActionWrapper pySubAction:runAct pzActivity:pzScanCode". Investigation showed this was due to the pzScanCode activity referred to in pzpega_control_actions_scanCode.js file not being registered, and has been resolved by adding code to register the necessary events for both button and navigation.

INC-174409 · Issue 661658

Article on "Specifying the content of a product rule" updated

Resolved in Pega Version 8.7.1

The documentation for the 'Class instances to include' section of the Rule-Admin-Product form has been updated to more clearly specify that the report definition used as a filter requires the inclusion of the pzInsKey property in the data returned from the report definition. This can be accomplished by either of the following: * Include pzInsKey 'Edit columns' (Query Tab) section of the report definition. --or-- * On the 'Data Access' tab, 'Row key settings' section, check the 'Get row key' checkbox (it will list the row keys for the class -- pzInsKey should be among them).

INC-195216 · Issue 686911

MSGraph documentation updated

Resolved in Pega Version 8.7.1

The documentation for using MSGraph has been updated to reflect that standard headers cannot be overridden.

INC-182245 · Issue 664456

Updated dedicated index reindexing check

Resolved in Pega Version 8.7.1

Attempts to reindex were not successful after a dedicated index failed with the error "Not enough active shards for index work to meet write consistency of quorum". This has been resolved by updating the system to validate the cluster state for the dedicated index name instead of the work index name when performing a dedicated index Reindex.

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