SR-B960 · Issue 271764
PDF "Display Report Filter" check honored
Resolved in Pega Version 7.2.2
The filter layout was visible in a generated PDF despite "Display Report Filter" being unchecked. This was the fault of a missed visibility condition in pzDisplayReportSectionForPDF, which has now been added.
SR-A89677 · Issue 257766
Removed erroneous warning from auto-created DataType reports
Resolved in Pega Version 7.2.2
When creating a data type and local source, a report definition is automatically generated for the data type. That report definition contains the warning "Using a custom HTML control to format a column may result in poor performance displaying query results. Consider using auto-generated HTML controls." This was confusing, creating the unintended assumption that something was wrong with the automatically generated report. To clarify this, the warning will not be displayed when the rule is created automatically.
SR-A96539 · Issue 264614
Report Definition parameter passing improved for grids
Resolved in Pega Version 7.2.2
When run report was configured on a grid, the Data-Click attribute for a Report definition action with the parameter of type Pagename.Prop inside the grid did not generate properly. The parameter passing has been improved to address this issue.
SR-A96539 · Issue 265411
Report Definition parameter passing improved for grids
Resolved in Pega Version 7.2.2
When run report was configured on a grid, the Data-Click attribute for a Report definition action with the parameter of type Pagename.Prop inside the grid did not generate properly. The parameter passing has been improved to address this issue.
SR-A91955 · Issue 260732
Filter icon made accessible
Resolved in Pega Version 7.2.2
When the Enable accessibility add-on was checked, the filter icon was not selectable. This has been corrected.
SR-A94690 · Issue 261686
Report Editor displays Associations
Resolved in Pega Version 7.2.2
When using a custom activity to display properties in the data explorer, the "More" link is not displaying the associations when added. This was an error in the logic which determined whether pyReportEditorProperties exists for the class or not, and has been fixed in pzGetCustomPropsForTreeGrid.
SR-A77395 · Issue 255085
DB2 external mapping values used for filtering
Resolved in Pega Version 7.2.2
When using the "External Mapping" feature in a class to map column names to different property names in DB2, the filter conditions in a report definition rule either generated incorrect SQL in the report viewer for "Select Values" or the error "There was a problem getting a list" appeared. This error was caused by the SQL query using the property name instead of the column name, leading to external mapping for the properties not being considered. The pzGetAvailableValues activity has been modified to get the correct column name based on external mapping.
INC-145293 · Issue 674901
Additional diagnostic logging added for ElasticSearch startup issues
Resolved in Pega Version 8.7
The PyIndexerState was stuck in Starting status during node initialization. This issue could occur if the filesystem became hung due to network level issue while scanning entries from /etc/mtab, resulting in a lock which was not released correctly. In order to better determine which node entry in a cluster may be responsible for the hang, an update has been made which will use a temporary virtual environment to repeat the part of the initialization phase responsible and generate additional logs for debugging. To activate this, the PegaSearch.Diagnostics logger must be set in DEBUG mode. This duplicated virtual initialization will not interrupt the normal initialization.
INC-153849 · Issue 641925
Updated replica management for search clusters
Resolved in Pega Version 8.7
When using a cluster with two Universal nodes in the cluster, a daily restart process where the second node was not started until the first was fully up resulted in Search initialization failing for the first node while becoming active on the second node. This was traced to the methods used in increasing and decreasing replicas. This has been resolved by revising the handling of ElasticSearch node lifecycle and replicas through a new option "Dindex.searchNodeCount " which includes a specification for the number of expected search nodes. If this option is not present, the old method will be used.
INC-160190 · Issue 658125
Logic updated to allow page property and declare index with the same name
Resolved in Pega Version 8.7
A Property which was in a Pagelist which in turn was embedded in a Page was not visible in the Report Browser. This was traced to the two properties sharing the same name, and was caused by a check which ensured only entries with unique names were added. In order to support this configuration, logic has been added to pzAddPropListForClass_TreeGrid such that if a page property and declare index share the same name, they are both added to the tree grid.