SR-D75097 · Issue 542359
DSS added to allow disabling Excel cell export security
Resolved in Pega Version 8.3.2
In order to avoid calculation injection during Export to Excel, an apostrophe character was added to the cell on export to close a vulnerability. However, sites using an external tool to consume the Excel document needed a workaround for this security feature. The resolution for this issue adds a DSS setting "TurnOffSecurityForExportToExcel" which can now be used to turn on/off the security feature that adds char " ' " in front of the cell value. Further refinements to this work will be included in a future release.
SR-D75757 · Issue 540638
ReportBrowser script updated to ensure older version refreshes on creation
Resolved in Pega Version 8.3.2
When using the old version of the Report Browser, the count at the report category did not update after being saved into a category until logout and login back to the portal. This was a missed use case for the old browser during updates to the UIKit and has been resolved by including the reportbrowser script in the header section pyCMReportBrowserHeader to ensure a refresh.
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.
INC-204672 · Issue 699355
Handling updated for database function GREATEST
Resolved in Pega Version 8.7.1
When deploying Pega on Red Hat OpenShift, attempting to index data via the SRS resulted in the landing page loading and RULES indexing appears to start, but when it finally completed it showed no records. While the index operation was running log entries showed the SRS service was unavailable and that the isolation context did not exist. Investigation showed there was an exception being generated indicating "com.microsoft.sqlserver.jdbc.SQLServerException: 'greatest' is not a recognized built-in function name". Because the function GREATEST is not supported in Microsoft SQL Server 2019, an update has been made to change GREATEST into an expression like "IIF(COALESCE(column_name, 0)>value, COALESCE(column_name, 0), value)" for compatibility.
INC-209688 · Issue 702729
Handling updated for database function GREATEST
Resolved in Pega Version 8.7.1
When deploying Pega on Red Hat OpenShift, attempting to index data via the SRS resulted in the landing page loading and RULES indexing appears to start, but when it finally completed it showed no records. While the index operation was running log entries showed the SRS service was unavailable and that the isolation context did not exist. Investigation showed there was an exception being generated indicating "com.microsoft.sqlserver.jdbc.SQLServerException: 'greatest' is not a recognized built-in function name". Because the function GREATEST is not supported in Microsoft SQL Server 2019, an update has been made to change GREATEST into an expression like "IIF(COALESCE(column_name, 0)>value, COALESCE(column_name, 0), value)" for compatibility.