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.
INC-195511 · Issue 693219
Check added for child join class when using ABAC
Resolved in Pega Version 8.7.1
When a join was applied on a report definition and the same join class had a child class to which ABAC was applied (for some property eg., isABC), an "invalidreference" exception (isABC) was generated. This was traced to the system taking into account the child class of the join class while running the report, and has been resolved by adding a check to handle this scenario.
INC-198273 · Issue 688355
DSS added to control BIX extraction time properties
Resolved in Pega Version 8.7.1
After upgrade from Pega 7.3 to Pega 8, downstream systems were failing to process the BIX extract manifest summary file. This was due to three columns which were introduced in Pega 7.3.1 to handle any failures during BIX incremental extraction: pxStartCommitDateTime, pxEndCommitDateTime, and pxLastSuccessFulCommitDateTime. To support better backwards compatibility, this fix introduces the below DSS to allow disabling of the new columns. BIX/disableSaveTimePropertiesInCSV BIX/disableSaveTimePropertiesInXML BIX/disableSaveTimePropertiesInDB
INC-200973 · Issue 699265
Added handling for client-side validation errors in sub-reports
Resolved in Pega Version 8.7.1
When a sub-report was trying to access externally mapped fields or an optimized page property by JOIN of another class, the main report was unable to validate the Page property. This has been resolved by updating the activity code to handle client-side validation errors on main reports attempting to access the externally-mapped Page properties of another class in the sub-report.