SR-B38674 · Issue 301022
Descendant class logic made more robust
Resolved in Pega Version 7.3
The 'Report on descendant' option in the report definition/Listview was giving incorrect results. This was caused by the code used to execute the RD looking up the descendant class from the current application that inherits from the applies-to class (tools.getDatabase().getConcreteDescendantsInCurrentApplication(class name);) of the RD and executing the RD against this class. While this is appropriate when an application is built on another and case types are directly inherited into the new layer, this will not work when application layers are added which do not include equivalent case types for every case from the built upon applications. This becomes a more common problem when the MBO feature starts getting used more often on the customer implementations. To ensure the descendant class is correct, the Useimplemenation class has been updated to be more robust.
SR-B11201 · Issue 281026
Downcasing added to ensure skin-defined templates are applied as expected
Resolved in Pega Version 7.3
When using a customized modal template and modal format defined in the application skin, the UI reflected the section modal template but not the skin template. This was traced to the CSS not being applied due to skin rule custom format names being case sensitive. To resolve this, code has been added to downcase the name when generating style for the modal.
SR-B38290 · Issue 295916
Fixed screen truncation with Mashup
Resolved in Pega Version 7.3
Screen content was truncated on refresh when using Web Mashup with Firefox and Microsoft Internet Explorer 11. The resize harness has been updated to call pega.Mashup in a timeout in order to fix this.
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-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-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.
SR-B16230 · Issue 287871
Dollar sign character will be escaped if present in data page value
Resolved in Pega Version 7.3
If a section was configured to show the data with a data page as source, using the dollar sign in the value caused the amount to not be displayed correctly in the grid. This has been corrected by adding code to escape the $ character when it's present in the data.
SR-B51793 · Issue 308487
Extended options for creating Context URI
Resolved in Pega Version 7.3
In order to facilitate the use of Amazon Web Services, an enhancement has been added to extend the methods available for forming Context URI. Previously, Pega Platform mandated both X-Forwarded-Host and X-Forwarded-Proto be present when using HTTP extension headers. The new feature adds HOST support when X-Forwarded-Proto is present without X-Forwarded-Host. The URL will consider X-Forwarded-Proto for protocol (http or https) and take the host name from host header. This change works for any reverse proxy or load balancer, as long as they emit X-Forwarded-Proto and preserve the HOST header.
SR-B38602 · Issue 296751
Login error message modified for increased security
Resolved in Pega Version 7.3
When an operator was configured to use External authentication and then attempted to login through other servlets, the error message included the operator ID. This could be used maliciously to discover valid IDs on the system, so in order to improve security, the process has been modified to remove the ID from the failure message. If authentication fails, the message "The information you entered was not recognized." will be displayed and the system will log an error message in the PegaRULES log file with the actual message "Error authenticating , : This user must use external authentication."