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-B13431 · Issue 283632
Mobile App description localized in PegaExpress
Resolved in Pega Version 7.3
The descriptions for Pega API and Pega Mobile SDK were not being localized in Pega Express due to limitations in the accepted characters. This has been fixed.
SR-B13431 · Issue 283681
Mobile App description localized in PegaExpress
Resolved in Pega Version 7.3
The descriptions for Pega API and Pega Mobile SDK were not being localized in Pega Express due to limitations in the accepted characters. This has been fixed.
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-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-B13785 · Issue 284733
Added tenant ID check for batch thread in MT environment
Resolved in Pega Version 7.3
When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.
SR-B13785 · Issue 284743
Added tenant ID check for batch thread in MT environment
Resolved in Pega Version 7.3
When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.
SR-B13785 · Issue 278965
Added tenant ID check for batch thread in MT environment
Resolved in Pega Version 7.3
When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.
SR-B15497 · Issue 286469
Styling corrected for last row in tree grid sourced from RD
Resolved in Pega Version 7.3
Tree grids sourced from report definitions had their last row set to the class "grandTotal" instead of "gridRow", causing them to get incorrect styling. This was caused by a missed cleanup for this use case when removing the GrandTotal class from support in RD, and has been fixed.