SR-A98230 · Issue 271051
Revision management GET logic revised
Resolved in Pega Version 7.3
When the revision manager creates a new revision, the second step is to add rules (strategies/data transforms etc.) into that revision so that a strategy designer can work on that. However, it was found that if one of the HTTP requests was of GET method, selecting the rules and hitting 'submit' constructed an oversized URL which listed all the rules listed on the Revision page and the browser would hang due to the GET exceeding the character limit. To avoid this, the logic used to create the post body has been modified to creating avoid long parameter values.
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-B10347 · Issue 279670
Attachment icons display correct type
Resolved in Pega Version 7.3
The attachment icon was not reflecting the attachment type. This was caused by an error in the pzWorkAttachmentIcon control which caused the File name to be passed as empty, resulting in a failure to fetch the correct image name. This has been fixed.
SR-B10406 · Issue 279344
Custom operator images work in IE
Resolved in Pega Version 7.3
Custom operator images (using pxOperatorImage control) were not properly displayed in the Internet Explorer browser. This was traced to a malformed URL generated by the pxOperatorImage control, and has been fixed.
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-B10826 · Issue 280564
Widget descriptions localized for Case Manager
Resolved in Pega Version 7.3
Localization has been added to the widget descriptions for "Team Worklist" and "Welcome to Case Manager".
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.