SR-A12684 · Issue 224534
Extracts count corrected when using XML as output
Resolved in Pega Version 7.2
While running an extract using XML as output, a difference was observed in the number of records being extracted when compared with 'Database Schema' as output. The Pega-BIX logs contained failed records with 'Index out of bounds' exceptions. This was traced to missing handling for the value group property references in this scenario, and has been corrected.
SR-A10974 · Issue 223153
BIX Manifest enhanced to include fully qualified property names
Resolved in Pega Version 7.2
If an page list property with the same name existed under two levels in the extracted data (specified in the extract rule multiple times), there was no way to differentiate them when viewing the BIX Manifest file. To resolve this, an enhancement has been added to ExtractImpl to include the fully qualified name for the property.
SR-A12324 · Issue 226656
XML manifest output support added for nodes with 'px' naming schemes
Resolved in Pega Version 7.2
When the 'pxSkillsRequired' value Group property was part of the properties being extracted, node names starting with px generated an exception while writing to XML manifest output format. Handling has now been added to support node names starting with 'px'.
SR-A14732 · Issue 228331
pxObjClass correctly applied to nodes for extract rule form
Resolved in Pega Version 7.2
If pxObjClass was selected for the top level node in the extract rule form, BIX would use use pxObjClass for all of the embedded nodes irrespective of whether pxObjClass was selected for the embedded node or not. If pxObjClass was not selected in the top level node but then selected for all of the embedded nodes, then the system would not use pxObjClass for any of the nodes. To correct this, changes have been made to ExtractImpl and BIXXMLStream so that pxObjClass will be added to those nodes for which pxObjClass property has been explicitly selected in the extract rule form.
SR-A15173 · Issue 229236
pxObjClass correctly applied to nodes for extract rule form
Resolved in Pega Version 7.2
If pxObjClass was selected for the top level node in the extract rule form, BIX would use use pxObjClass for all of the embedded nodes irrespective of whether pxObjClass was selected for the embedded node or not. If pxObjClass was not selected in the top level node but then selected for all of the embedded nodes, then the system would not use pxObjClass for any of the nodes. To correct this, changes have been made to ExtractImpl and BIXXMLStream so that pxObjClass will be added to those nodes for which pxObjClass property has been explicitly selected in the extract rule form.
SR-A12638 · Issue 223936
Check added to handle mismatched property names given in referred page
Resolved in Pega Version 7.2
If a property name was provided in a list criteria by referring page name, it generated type mis-match error even though the property was of the same type. Creating a new RD with same criteria avoided this error, but a check has been added to "Validate_Report_Condition" to determine whether the property is a leaf or page property . If it is a page property, the system will prefix that property with a "." to resolve the mis-match issue.
SR-A7008 · Issue 216642
Number separators localized for Excel export handling
Resolved in Pega Version 7.2
While using the Export to Excel button in reports, some of the figures in numbers columns displayed warning messages indicating they were formatted as text. This was a localization issue where numbers containing unusual separators were interpreted as strings, and has been resolved with a code change that allows Excel to decide the right format based on locale.
SR-A5758 · Issue 218426
Corrected automatic decimal rounding in summary report
Resolved in Pega Version 7.2
In the summary view report grand total, decimal values having 4 digits after the decimal point were being rounded to two places and displaying two zeroes in the 3rd and 4th decimal places. Ex: 1.1234 + 2.2345 returned 3.3500 instead of 3.3579. This was traced to the format "#.##" being applied to every value in the summary, and has been corrected.
SR-A7716 · Issue 219147
Proper value separations in filtered report definitions
Resolved in Pega Version 7.2
In a report definition in edit mode, trying to set filtering on several value was causing values to be appended without proper separators. As a result, no results were found when trying to apply a filter. This was due to a conflict in visibility conditions for the DataType identifier , and has been fixed.
SR-A10501 · Issue 223738
Corrected date format for chart using custom DateTime filter
Resolved in Pega Version 7.2
The date format of legends for a chart was not being formatted properly if a Filter Criteria range was used on the Datetime property. This has been corrected.