SR-A99678 · Issue 272068
Chart clipboard page unloaded properly in tab refresh
Resolved in Pega Version 7.3
When a portal tab containing a chart was refreshed due to use of the "refresh when active" tabbed layout checkmark, the old chart clipboard pages remained. This was due to a missed use case, and has been fixed.
SR-B10018 · Issue 280365
Null pointer resolved for change events
Resolved in Pega Version 7.3
On a section where a grid had at least one column cell with the visibility condition configured to be run on client, each data change event on other controls inside the same section raised a JavaScript error which disabled all of the following actions configured to be executed on the change event. These script errors were due to the improper usage of the findCell API call, resulting in the second parameter always being sent as null. To correct this, the getElementRowPageRef of pega_ui_doc_eventsConditionChaining.js has been updated to pass the grid parent table properly for findCell to avoid a null pointer.
SR-B10076 · Issue 281632
Save and Cancel use case enabled
Resolved in Pega Version 7.3
When a button was configured with both the "Save" + "Cancel" out-of-the-box actions, the cancel action was performed but the data was not saved to the database. If the button was configured only as a Save action, the save worked as expected but the lock was not released. In order to support a CrossDomain windows use case of enabling an agent to save entered work but cancel out of the case so another another agent can pick up the case and continue with it, the Work-Autoclose function has been modified to write try catch blocks and call doClose when a button is configured with both the "Save" + "Cancel" out-of-the-box actions.
SR-B10620 · Issue 281882
Fixed disappearing cell value in grid row
Resolved in Pega Version 7.3
Entering a value in the first grid row cell configured with a post action change and then clicking outside of the cell caused the cell to disappear the first time, but worked as expected on subsequent clicks. This was caused by the postvalue action context parameter being lost, and has been corrected by adding an alternate way to get the active row in case it is not found using the getActiveRowIndex API
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-B1095 · Issue 274113
ReadOnly correctly propagates to child section in FreeForm
Resolved in Pega Version 7.3
When using FreeForm layout, the read-only edit option conditions of the parent were not getting evaluated on the innermost nested section display. The GridSectionBodyElements RUF has been updated to correct this.
SR-B11141 · Issue 282453
PageList property popup fixed in Report Editor
Resolved in Pega Version 7.3
When adding a PageList property to a report in the Report Editor, the resulting popup was empty. This was caused by a missing layout in the section used to display the index of the pagelist, and has been fixed.
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-B11271 · Issue 281717
Assignment Gadget hang resolved
Resolved in Pega Version 7.3
The Open Assignment Gadget was hanging when loading assignments in perform harness, preventing completion of the assignment. This was due to a missing null check for dataRow in the setHeadersWidth API for grid generation, and has been fixed.
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.