SR-B12474 · Issue 282643
BIX extraction config documentation updated
Resolved in Pega Version 7.3
When using command-line BIX 7.1 to extract records and write them to a secondary database, it appeared that some of the records got skipped. This was actually expected behavior: as the records got updated while the extract was running, those particular updated records got skipped as they did not fall into the time range that user was passing. To eliminate this confusion, the log message has been clarified. In addition, the information in the Guide indicated that if bix/useHistoryClasses was set to true, the generated query should always use the history table and not the actual work object table. However, it was not made clear that the BIX code does not use this option for explicit command line arguments. Therefore, the following text has been added to the BIX documentation under "Configuring the extraction environment" -> "Configuring optional prconfig.xml settings": Including class instances added during a batch run To ensure that class instances added to the Pega Platform database after a batch run begins execution are included in the extract, add the following property:
SR-B12714 · Issue 294429
String comparison logic updated for complex property references
Resolved in Pega Version 7.3
Running a report that has a single page property (.Address.pyCountry) generated an error and the report shows no results. It worked correctly if the column is removed or a filter was added on instances that have .Address.pyCountry not null. This was an issue related to string comparisons, and has been resolved by updating the logic for parsing of complex references in UDFs.
SR-B13016 · Issue 284134
Report title shows for exported Excel; display report label name reverted
Resolved in Pega Version 7.3
Exported Excel reports were not showing the report title if the "display report filters" checkbox was unchecked in the RD rule. If the box was checked, the report title turned up in the Excel sheet, but the report UI showed an unnecessary blue bar if none of the filter criteria were set to be displayed as per business needs. The missing report title was traced to an error in the "display report filters" checkbox, and has been fixed. Additionally, the 'display report header' label in the pzReportViewerUserActions section had been recently modified to read 'display report filters', which was misleading - that change has been reverted.
SR-B13606 · Issue 287616
Angle brackets escaped for RD drill down
Resolved in Pega Version 7.3
In a report definition with drill down, if the column parameter had a value that used the wrong parameter was getting passed in Query. This was due to the characters getting converted into their HTML equivalent < and >., and the character escaping has been corrected to resolve this.
SR-B13647 · Issue 291863
Security Policy updates to handle big strings
Resolved in Pega Version 7.3
The implementation of a "one of" Access Control Security Condition that took the list from a Data Page was failing SQL construction due to the string exceeding 4000 chars. To resolve this, support has been added to SetClob() for page references, changes have been implemented in for the AllOf and OneOf functions, and a new property 'pyParameterValueUpdated' has been added to the Pega-RulesEngine.
SR-B13647 · Issue 291683
Security Policy updates to handle big strings
Resolved in Pega Version 7.3
The implementation of a "one of" Access Control Security Condition that took the list from a Data Page was failing SQL construction due to the string exceeding 4000 chars. To resolve this, support has been added to SetClob() for page references, changes have been implemented in for the AllOf and OneOf functions, and a new property 'pyParameterValueUpdated' has been added to the Pega-RulesEngine.
SR-B13775 · Issue 293697
Resolved error in adding Association's Page Property in report browser
Resolved in Pega Version 7.3
Adding an Association's Page Property while creating a report in the Report browser generated an error on the screen. This was caused by incorrect passing of the class, and has been corrected.
SR-B13775 · Issue 286916
Resolved error in adding Association's Page Property in report browser
Resolved in Pega Version 7.3
Adding an Association's Page Property while creating a report in the Report browser generated an error on the screen. This was caused by incorrect passing of the class, and has been corrected.
SR-B13931 · Issue 286184
BIX extract Inskey error fixed for nested page lists
Resolved in Pega Version 7.3
BIX Extract was failing with the message "Inskey of the corrupt Instance" if it encountered nested page lists. To resolve this, the PropertyReferenceImpl.filter() method will add missing elements in cases with nested pagelists.
SR-B14109 · Issue 292263
Fixed autocomplete for strings containing plus sign
Resolved in Pega Version 7.3
Autocomplete was not working properly when a search string contained the '+' sign. When the search input was passed to the DB, the + sign was changed to + in the query and therefore did not return any results. This was due to the parameter being encoded twice as it was passed from autocomplete to the grid infrastructure, and has been resolved by preventing the unneeded encoding.