SR-A100292 · Issue 270065
Select Values from join properly displayed on chart
Resolved in Pega Version 7.3
In charts of report definitions using a join, properties with prompt select values were displaying the actual data rather than the prompt values. This was due to a handling difference for properties from joins: before rendering the chart, report data was copied to a page that did not have the correct pxObjClass, creating the assumption that the property applied to @baseclass. To resolve this, the class will be set on the page that contains the target property.
SR-A103079 · Issue 273545
Check added for RD date time values
Resolved in Pega Version 7.3
An exception was generated when running RD by choosing the relationship for a datetime property as "Is not null" in filter conditions before displaying the data. This has been fixed with the addition of a check for the date time value.
SR-A21111 · Issue 268559
Performance improvements for embedded page reference checks
Resolved in Pega Version 7.3
Significant performance differences were seen between opening custom rules in the developer portal and opening the same rules in an embedded page. This was traced to each embedded page in the stream checking to see if reference properties are present. To resolve this, DirectStream has been modified to cache the value of containsAnyReferenceProperties if it has already been checked so that it is not repeatedly checked when it is not necessary.
SR-A92512 · Issue 270130
WebLogic tool generation updated for complexType schema
Resolved in Pega Version 7.3
A red X error was seen for PRAsync MDB modules on the Resource Dependencies screen in the WebLogic console in deployments with WebLogic 11i or 12c. This was due to the EJB component (prbeans.jar) not being implemented to support complexType schema, and has been resolved by updating the Pega Platform WebLogic components to support complexType schema in the WebLogic tool generation.
SR-B10345 · Issue 281585
Command line jar import handling improved
Resolved in Pega Version 7.3
When installing Smart Dispute and related strategic applications, exceptions occurred when generating a DDL via prpcUtils (e.g. prpcUtils.bat generateDDL) if any of the files listed in schema.archive.input did not contain schema changes or did not have a delta. This has been resolved by updating the system to better handle files that do not require a DDL to be generated.
SR-B10828 · Issue 282620
Surrounding spaces trimmed from property labels to ensure localization
Resolved in Pega Version 7.3
Property labels in the add reports screen were not localized because the value was given as "Contact Channel " with a trailing space. To resolve this, the pzReportExplorerNode control has been updated to trim leading and trailing spaces before performing localization.
SR-B11379 · Issue 281867
Backwards compatibility added for imported RDs to ensure Export to PDF option given
Resolved in Pega Version 7.3
After upgrade, the Export to PDF option was not visible under actions. This occurred when the Report Definition exported from an earlier version did not contain the property "pyUI.pyUserInteractions.pyShowDataOnly" in the rule XML, causing the 'when' rule pzShowExportToPDFLink to be evaluated to false. To correct this, the pzUpgradeOnOpen Data-transform has been modified to create the pyShowDataOnly property and assign it to false if it was not present or if the value is empty/null so the Export option will appear as expected.
SR-B11675 · Issue 284417
Cursor correctly changes to hand in Report Wizard popup
Resolved in Pega Version 7.3
The hand icon was not displaying as expected when the cursor was placed on the Search icon in the "Report Wizard" pop up window. This has been fixed.
SR-B11776 · Issue 289458
Report results populating as expected for tree grid
Resolved in Pega Version 7.3
Report definition results were not populated in the tree grid structure but were populated in the spread sheet structure. This was caused by a difference in handling for formatting a column with empty values, and has been changed.
SR-B12581 · Issue 282710
Documentation correction for setupDatabase.properties naming
Resolved in Pega Version 7.3
The install, upgrade, and update guides on the PDN referring to the setupDatabase.properties file properties gave erroneous name formats for the schema name properties. All instances in the documentation referring to pega.rules.schema have been changed to the correct format of rules.schema.name, and all instances of pega.data.schema have been changed to the correct format of data.schema.name.