SR-C74650 · Issue 422907
Grid alignment and headers corrected for Opportunities screen in RTL locale
Resolved in Pega Version 8.3
When using the RTL locale, the Opportunity detail screen and search screen had grid alignment and header issues. This has been resolved by updating the py-portal-stages CSS attached to the enduser skin.
SR-C83615 · Issue 424945
Support added for hiding unwanted category reports
Resolved in Pega Version 8.3
After upgrade, a customization used to hide unwanted out-of-the-box category reports was not working. This was due to the pyServiceLevelPerformance and pxSimulations category rules not being included as part of the pyOOTBVisibleInBrowser 'when' rule that is specified for Display in the report browser 'when' setting. These two category rules - pxSimulations and pyServiceLevelPerformance - have now been modified to reference the 'when' rule pyOOTBVisibleInBrowser so categories may be hidden as desired.
SR-B11192 · Issue 282623
Focus fixed for pxOperatorImage control
Resolved in Pega Version 7.3
When using pxOperatorImage control, the 'Tab' and 'Enter' keys were not usable to reach the Operator menu. This has been fixed by adding a tabindex attribute on the html tag of pxOperatorImage control to ensure proper focus.
SR-B35821 · Issue 296032
Extra space removed from "Filters: " in RD
Resolved in Pega Version 7.3
When a Report with a large number of columns was generated using Report Definition with enable add filters checked in the report definition rule, an unnecessary space appeared between the "Filters:" label and the filters. This has been removed.
SR-D26784 · Issue 507135
Check added to ensure client side validation checkbox is honored in Case Worker portal
Resolved in Pega Version 8.2.4
When the "Enable client side validation" checkbox on the Perform harness was unchecked, the validation was still firing when using a tab out on the Case Worker portal. The validation did not fire on tab out in the Case Manager portal, and both portals worked as expected on Submit. This was traced to the validation being fired without checking the value of the bClientValidation property. To resolve this, a check has been added to ensure the validation is fired only when it is set to true.
SR-A102222 · Issue 270905
Command line BIX extract includes pzinskey in XSD
Resolved in Pega Version 7.3
When running an extract to XML from within the UI, the generated XML and XSD both include the pzInskey. However, when the extract rule was saved to a file and run from the command line using the -I option, the XML file had the pzInskey but the XSD file did not. This has been corrected by ensuing the pzInsKey is included as part of XSD generated with the -I option.
SR-D3405 · Issue 439258
URL construction logic updated for Tracer
Resolved in Pega Version 8.3
When trying to trace a requestor from the requestor management landing page, a 400 bad request error was generated. Investigation showed that when forming the tracer URL, the pxRequestor.pxRequestorPathInfoInReal property was being appended to it. Because the property contained unencoded characters([), the request was not being processed. To resolve this, the URL construction logic has been changed to use pxThread.pxReqBaseURI.
SR-D39236 · Issue 508454
Corrected viewing of sorted drill-down spreadsheet-style summary reports
Resolved in Pega Version 8.2.4
When using a report with a summarized column and the 'Do not display group headings' grouping option checked, drill down was not working when the report was primarily sorted by default on any column other than the first one. This manifested as either no results returned by the drill down report or an error message related to invalid filter values. This was traced to the unique column ordering logic for non-spreadsheet-style summary reports being applied to the drilldown of spreadsheet-style summary reports due to the logic for creating the drilldown filters using the != operator to compare the spreadsheet flag string to the string constant "true". This previously worked as expected because this string was interned in the engine, but these string internments have since been removed. To correct this, pzPopulateReport has been updated to appropriately recognize spreadhseet-style summary reports as they used to.
SR-D26223 · Issue 502751
Corrected viewing of sorted drill-down spreadsheet-style summary reports
Resolved in Pega Version 8.2.4
When using a report with a summarized column and the 'Do not display group headings' grouping option checked, drill down was not working when the report was primarily sorted by default on any column other than the first one. This manifested as either no results returned by the drill down report or an error message related to invalid filter values. This was traced to the unique column ordering logic for non-spreadsheet-style summary reports being applied to the drilldown of spreadsheet-style summary reports due to the logic for creating the drilldown filters using the != operator to compare the spreadsheet flag string to the string constant "true". This previously worked as expected because this string was interned in the engine, but these string internments have since been removed. To correct this, pzPopulateReport has been updated to appropriately recognize spreadhseet-style summary reports as they used to.
SR-B15858 · Issue 286667
Fixed Right align of header in repeating grid
Resolved in Pega Version 7.3
When a Repeating grid was included in a section and the header used apply alignment as Right, the results did not display as expected. This was due to missing styles corresponding to Header Label Align class, which have now been added.