INC-230911 · Issue 740100
Apply filter option handles passed data page reference
Resolved in Pega Version 8.8
The GetGridColUniqueValues activity was failing on step 3 when the data page reference was passed as a parameter of source report definition in a grid. This was traced to missing filter parameters for this use case and has been resolved.
INC-231721 · Issue 741742
Dataview API correctly returns value for embedded fields
Resolved in Pega Version 8.8
n QueryableDataViewTransformer, pxObjClass is populated when the payload has no embedded fields and special processing is not required. Because of pxObjClass being present, the values are parsed as per the property type and correctly populated on the clipboard and a boolean is generated correctly in the response. However, when the payload has embedded fields and special processing is required, the response body was not populated with pxObjClass and hence all fields on the clipboard were treated as strings and the data view API responded with the values in as a string irrespective of type. To resolve this, page properties have been enabled in the aggregation validator and the transformer in QueryableDataViewTransformer.java has been refactored to link the property definition.
INC-231797 · Issue 738503
Restored Export to PDF for summary view
Resolved in Pega Version 8.8
Clicking the Export to PDF button from Summary view did not create the document and no events were generated in the tracer or logs. This was traced to a naming error in "appendSecurityTokens" on the SummaryViewHeader and has been corrected.
INC-232010 · Issue 740693
Report filter error message persists on the screen
Resolved in Pega Version 8.8
When attempting to use an invalid report filter such as "past 14 days" when that timeframe was not available, the error message appeared briefly and then disappeared. Investigation showed the runReport activity pzResolveCopyFilters activity was called and caught the “Invalid value” exception, however the system continued to proceed so the error message did not persist in the screen. This has been resolved by adding a jump condition to step 2 of pzResolveCopyFilters on StepStatusFail to preserve the error message.
INC-232127 · Issue 741807
View history export updated for BAC
Resolved in Pega Version 8.8
A 403 error was generated when trying to click Export to Excel in view history. Investigation traced this to the Export to Excel activity not being registered with basic access control, and this has been resolved by modifying the URL formation to pass the necessary parameters to register the activity in the menu harness.
INC-173596 · Issue 673104
Apache Commons HttpClient dependency removed
Resolved in Pega Version 8.8
As part of moving from the Apache Commons HttpClient project (which is at end of life and no longer being developed) to the Apache HttpComponents project, openws dependencies on the commons-httpclient jar have been removed.
INC-188127 · Issue 678350
Updated cache key generation for ROPC
Resolved in Pega Version 8.8
After configuring outbound email functionality using MSGraph with OAuth 2.0, sending the emails failed consistently following passivation. Running "Test connectivity" in the Email Account data instance then seemed to restart the functionality and the automation "Create And Send Email" subsequently worked. This was traced to a missing username in the cache key generation for the Resource Owner Password Credentials (ROPC), which caused the same token to be fetched when attempting to dynamically generate different usernames, and has been resolved.
INC-194865 · Issue 695620
Corrected report definition save-as-image option
Resolved in Pega Version 8.8
Attempting to save a report definition as an image resulted in an access denied error stating "Browser fingerprint validation failed : A request was received with an invalid or missing browser fingerprint. The request was denied", and the user session was closed. The security SECU0017 alert is generated when a request is sent to a Pega application and the browser fingerprint is either missing or does not match the expected value. The system tries to check the type of request for every requestor ID and fetch the CSRF token, but in this case it was not matching with the token present on the requestor thread. This has been resolved by adding scripts to send the hidden input value needed.
INC-198571 · Issue 708634
SSO update
Resolved in Pega Version 8.8
In order to ensure shared SSO direct links are used as intended, an update has been made which will explicitly require re-authentication for each use of a direct link.
INC-202702 · Issue 713725
Ruleset creation process updated to maintain thread scope
Resolved in Pega Version 8.8
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.