SR-A17649 · Issue 233752
SQL generation modified for "Optimize for Reporting"
Resolved in Pega Version 7.2.1
After using the wizard to update Properties via "Optimize for Reporting", Report Definition will create SQL that is unique if the optimized property name is too long. This can result in the unique property name exceeding the 30 character field length, which then triggers the generation of a unique id with P +timestamp as the column alias name. Unfortunately, this means even if the same report is executed multiple times, the query would be different each time because of the column aliases and therefore the DB engine won't take the benefit of prepared statement caching and performance could be effected. To create the most effective performance, the column alias generation has been modified as below to make the column alias the same across multiple runs of RD: - using 25characters in propertyname and suffix it with index of the field location in RD select, L for list report - using 25characters in propertyname and suffix it with index of the field location in RD select, G for group fields in summary report
SR-A19297 · Issue 237347
Added ability to set custom HTTP security headers
Resolved in Pega Version 7.2.1
XSS protections were interfering with the ability to set custom HTTP headers. To enable this, the system will use dynamic system settings from http/responseHeaders and add them to every HTTP response.
INC-173505 · Issue 657024
Error message updated for data page with REDUX
Resolved in Pega Version 8.7
A WrongModeException was generated when a runtime activity was trying to access a missing property in a data page with REDUX enabled. To clarify the issue, the error has been modified to be a MissingPropertyException. In addition, property information for a page group property was inferred on the top level page when it should have been inferred on the embedded page. This has been changed to infer the correct property information for mode-based processing to work as expected.
SR-A14283 · Issue 232771
Service request retry works in async mode
Resolved in Pega Version 7.2.1
The Retry mechanism has been modified to correctly pass the child requestor's status when service is configured in async mode.
INC-197112 · Issue 689260
Corrected unnecessary Severe Warnings for MSGraph account
Resolved in Pega Version 8.7
After configuring an email account with MSGraph settings and saving the the email account instance, three unneeded severe guardrail warnings were generated related to using D_pxGetApplicationSettingValue instead of a constant value. This has been resolved.
INC-191033 · Issue 684370
Security updated for viewing data tables
Resolved in Pega Version 8.7
In order to improve security related to viewing data table instances, the privilege pxListClassRecords has been created in @baseclass and added to the "may start" activity ListEditor. Please add the privilege pxListClassRecords to access groups using ListEditor.
INC-187750 · Issue 675635
Error message removed for adding a new datatype to a branch
Resolved in Pega Version 8.7
Clicking 'add data type' for an application when no unlocked rulesets were available resulted in the error message "No unlocked Rulesets/Versions found that are valid for this record. Unlock at least one Ruleset/Version that can contain records of this type.". However, it was possible to create a data type by choosing branch. Investigation showed this message was added by the activity pzLoadTypeToBeAdded and is not needed: it has been removed from the step that appended the message when validating on click of submit.
INC-175672 · Issue 655809
ServicePackage thread handling improvements
Resolved in Pega Version 8.7
Work recently done to improve the release of requestor pool threads for the ServicePackage has been further enhanced by adding an explicit status notification to the thread waiting for Data Pages to be loaded in background and added support for the use case of a missing object handler.
SR-A14841 · Issue 234741
Multiple message deletion updated in MQ Server and MQ Explorer
Resolved in Pega Version 7.2.1
When multiple messages on the MQ Server and MQ Explorer queues were selected and deleted, only the first message was deleted. This has been corrected.
SR-A14841 · Issue 234742
Multiple message deletion updated in MQ Server and MQ Explorer
Resolved in Pega Version 7.2.1
When multiple messages on the MQ Server and MQ Explorer queues were selected and deleted, only the first message was deleted. This has been corrected.