SR-A19659 · Issue 241725
Autocomplete accepts parameters with special characters
Resolved in Pega Version 7.2.1
Autocomplete was not populating results when it was configured with a Datapage which accepted parameters and those parameters included colons. The handling for the function,"updateParams" (of pzpega_control_autocompleteag.js) has bene modified to send the parameter in the request body instead of the header.
SR-A23686 · Issue 249793
Support extended for NUMERIC types in RD SQL joins/filters
Resolved in Pega Version 7.2.2
Support has been extended for NUMERIC types in Report Definitions, more specifically to support references to NUMERIC properties in join and filter conditions in RDs using SQL Server 2012, by updating the IDENTITY column type handling in the RUF pzCheckCompatibilityOfColumnTypes function.
SR-A23686 · Issue 248675
Support extended for NUMERIC types in RD SQL joins/filters
Resolved in Pega Version 7.2.2
Support has been extended for NUMERIC types in Report Definitions, more specifically to support references to NUMERIC properties in join and filter conditions in RDs using SQL Server 2012, by updating the IDENTITY column type handling in the RUF pzCheckCompatibilityOfColumnTypes function.
SR-A91225 · Issue 259591
Support extended for NUMERIC types in RD SQL joins/filters
Resolved in Pega Version 7.2.2
Support has been extended for NUMERIC types in Report Definitions, more specifically to support references to NUMERIC properties in join and filter conditions in RDs using SQL Server 2012, by updating the IDENTITY column type handling in the RUF pzCheckCompatibilityOfColumnTypes function.
SR-B41833 · Issue 297708
Modal size remains consistent
Resolved in Pega Version 7.3
The modal size increased if a small bonus modal was reopened after a large modal was viewed. This has been corrected by modifying the logic in the modalDialogCallBack function(pega_ui_modaldialog.js) to set modal dimensions after setting the class from callbackargs.
SR-B93784 · Issue 341474
Validate rule can add another under a page
Resolved in Pega Version 7.4
Trying to add a row inside a validation rule by mapping a Page property to call validate was not working. This was due to pyEcho (which is used to hold the function) being validated for empty string even though the property was of page type, and has bene fixed.
SR-C16693 · Issue 359290
Column name shows in filter section RD of drilldown report
Resolved in Pega Version 8.1
The Column name in the drilldown filter was displayed as a function in the 'column source' (of the main report definition) in the drilldown report, but the name was not provided in the 'column name' column in the query tab of the main report definition. This has been corrected.
INC-156178 · Issue 637676
IOException logging changed to warn
Resolved in Pega Version 8.4.5
JBoss error messages related to "Exception occurred while closing the Stream" were appearing as a side effect of load on the system or network issues. As this is not a functional concern, the logging for these exceptions has been changed so they will only be shown if warn is enabled.
SR-D86360 · Issue 548570
Handling added for declare expression targets when harnessid is null
Resolved in Pega Version 8.3.3
Client expression calculation was not happening in Perform harness. Research showed that whenever text input calculations happened, the expression_calculation js setTargetValuesSuccess function was called but the elementList parameter was passed as null due to the inputHarnessId parameter being undefined. This has been resolved.
SR-D86360 · Issue 548572
Handling added for declare expression targets when harnessid is null
Resolved in Pega Version 8.4.1
Client expression calculation was not happening in Perform harness. Research showed that whenever text input calculations happened, the expression_calculation js setTargetValuesSuccess function was called but the elementList parameter was passed as null due to the inputHarnessId parameter being undefined. This has been resolved.