INC-137009 · Issue 581892
Ad hoc reports saved successfully in private categories
Resolved in Pega Version 8.5.1
After upgrade, an error was seen when attempting to save an ad hoc report in a private category. Saving in a public category worked as expected. This was traced to the Rule-Shortcut.Validate activity, which attempted to use the Rule-Shortcut's RuleSet to find the Rule-Category. To resolve the saving issue, the Rule-Shortcut.Validate activity has been updated to do an Obj-Open on the Category instead.
INC-136643 · Issue 583367
Orphaned CSS reference removed from DisplayReport harness
Resolved in Pega Version 8.5.1
An intermittent invalid CSS error was appearing in the DisplayReport harness when an operation resulted in the regeneration of the harness content. This was traced to a reference to the workform_pyReportingSkin CSS, which was used in old reporting features and is not in use anymore. The reference has been removed to resolve this issue.
INC-131942 · Issue 574321
Orphaned CSS reference removed from DisplayReport harness
Resolved in Pega Version 8.5.1
An intermittent invalid CSS error was appearing in the DisplayReport harness when an operation resulted in the regeneration of the harness content. This was traced to a reference to the workform_pyReportingSkin CSS, which was used in old reporting features and is not in use anymore. The reference has been removed to resolve this issue.
INC-135719 · Issue 580691
Corrected reference exception for filter on a grid sourced from a parameterized report definition
Resolved in Pega Version 8.5.1
An Invalid Reference Exception was thrown after attempting to apply a filter on a grid sourced from a parameterized report definition. This was traced to work done to allow cross-scripting filters to allow filters to contain special characters, and has been resolved.
INC-137317 · Issue 585402
Security improved for searches
Resolved in Pega Version 8.5.1
Authentication requirements have been added to activities associated with searching.
INC-125641 · Issue 573384
Column Filter working with class join
Resolved in Pega Version 8.5.1
When a class join was configured in the report definition and the report was edited to include new columns from the joined class, a "Filter condition invalid" error appeared in the tracer after adding a filter condition to a new column. This was only observed when the property added was a decimal property, and did not happen for a text property. The filter worked as expected after re-saving the property in the report definition in Designer Studio. This was traced to the data type being passed as "DECIMAL" for decimal fields, which did not match the logic used to set the filter value, and has been resolved.
INC-132169 · Issue 584759
NativeSQL will use inline rule resolution for core components
Resolved in Pega Version 8.5.1
After upgrade, nodes were going down with a heartbeat error. This was traced to issues with NativeSQL taking a very long time to generate queries due to the overhead in calling multiple complex functions to resolve rules. To correct this, updates have been made to resolve the standard set of functions used by core components inline in NativeSQL function resolution.
SR-B65131 · Issue 330322
Fixed 'when' rules for showing privileged escalation buttons
Resolved in Pega Version 7.4
Privileged escalation was displayed for a user with access to manager reports due to missing 'when' rules for hiding the Add report/Add category buttons. This has been fixed.
SR-B67967 · Issue 330128
Data explorer displays all associations and optimized nested properties are supported
Resolved in Pega Version 7.4
The rule resolved RDB query used to list the associations for the report class was not returning all associations. The logic for this has been modified to use a rule resolved report definition to correct the issue. In addition, the pzAddPropListForClass_TreeGrid function has been refactored in order to correctly support nested properties.
SR-B67967 · Issue 331406
Data explorer displays all associations and optimized nested properties are supported
Resolved in Pega Version 7.4
The rule resolved RDB query used to list the associations for the report class was not returning all associations. The logic for this has been modified to use a rule resolved report definition to correct the issue. In addition, the pzAddPropListForClass_TreeGrid function has been refactored in order to correctly support nested properties.