SR-B51933 · Issue 314418
Fixed RD shortcut for opening multiple reports in multiple tabs
Resolved in Pega Version 7.3.1
When a Report Definition was launched via Navigation -> Actions -> Run Report and Target was selected as 'New Document', multiple reports were not opening in multiple tabs side by side. Instead, when the previous report tab was closed the new one was opened. The display worked as expected when Target was selected to be 'Replace Current' or "Open in Pop-up" or if the entire browser was refreshed. The issue was traced to an incorrect calculation in a short cut handle, and has been fixed.
SR-B54906 · Issue 313350
Column calculations fixed for RD exported to Excel
Resolved in Pega Version 7.3.1
When exporting a report definition that contains calculated columns to Excel, the columns were either blank or 0% for each row even though the correct calculated values appeared in both the HTML preview and the PDF export. Additionally, date formatting was not applied in the Excel export. This was due to legacy code inserted in an earlier version of Pega to repair Export to Excel; the fix is no longer necessary since the exporting function was reworked, and has been removed.
SR-B48373 · Issue 306064
App Explorer enhanced to support expanded number of built-ons
Resolved in Pega Version 7.3.1
When the number of built on applications was more than 50, Application Explorer did not display all the results. This was a legacy issue: at the time the report definition code was developed there was no support for multiple built-on applications. The max records for the query for validating the application chain was not configured, resulting in a default value of 50. In order to support more complex use, pyMaxRecords is now set to 0.
SR-B49305 · Issue 307379
XSS filtering added to Chart Title
Resolved in Pega Version 7.3.1
XSS security filtering has been added to the Chart Title in the Chart Editor.
SR-B52024 · Issue 308435
XSS filtering added to Chart Title
Resolved in Pega Version 7.3.1
XSS security filtering has been added to the Chart Title in the Chart Editor.
SR-B66996 · Issue 312205
Access control policy logic added for non-work/data/assign classes
Resolved in Pega Version 7.3.1
As part of ABAC (Attribute-based access control) restrictions, if a class property was of type PageList, security had to be created in the PageList property class type. However, if the pagelist was of type "Embed-" class then it was not possible to create security policy due to the inability to apply property masking for page list properties of that class. To resolve this, property masking implementation logic has been added to support page list properties of non-work/data/assign classes for access control policies.
SR-B66996 · Issue 315524
Access control policy logic added for non-work/data/assign classes
Resolved in Pega Version 7.3.1
As part of ABAC (Attribute-based access control) restrictions, if a class property was of type PageList, security had to be created in the PageList property class type. However, if the pagelist was of type "Embed-" class then it was not possible to create security policy due to the inability to apply property masking for page list properties of that class. To resolve this, property masking implementation logic has been added to support page list properties of non-work/data/assign classes for access control policies.
SR-B55119 · Issue 312817
Handling added for absent property in Access When
Resolved in Pega Version 7.3.1
Configuring Access Control Policy to automatically restrict access to certain records by including an Access When rule to compare a custom property (.Consultant) on the OperatorID (Data-Admin-Operator-ID) page generated an exception if that property did not actually exist on the current operator. This has been resolved by revising the security policy engine to handle the exception.
SR-B71077 · Issue 323027
IDP Encrypted connections working on SAML
Resolved in Pega Version 7.3.1
IDP initiated SAML 2.0 was not working, and generated the error "Unable to process the SAML WebSSO request : Missing Relaystate information in IDP Response". Authentication worked fine with unencrypted SAML token. This schema validation failure happened because encrypted attributes were previously being ignored by Pega due to an issue in the underlying openSAML library. To resolve this, a custom PegaSAMLValidator has been inserted to validate the assertion and honor encrypted attributes.
SR-B56328 · Issue 312168
RARO rules more secure against deletion
Resolved in Pega Version 7.3.1
In order to make RARO rules more secure, the system has been updated such that Class Permissions can't be deleted from the role unless the operator has permission and is operating in a valid context (unlocked ruleset). This has been done by revising the Role rule form to disable the delete button when RARO/RADO is in a locked ruleset.