SR-B9780 · Issue 286188
work object progression fixed after cancel/close with errors
Resolved in Pega Version 7.3
A repeat grid's modal dialog could be cancelled or closed without correcting the validation error fired by a field in it, but afterwards no actions could be performed on that specific work object even if the error was then fixed. This was caused by Messages added onto the pyWorkPage not being cleared on click of cancel if followed by clicking on grid pagination actions, and has bene resolved by changing the cancelmodal method from ModalButtonSubmit to ModalButtonCancel.
SR-B9879 · Issue 278433
RTE linkbox input handling corrected for modal windows
Resolved in Pega Version 7.3
In an "inline editable" grid with 'click to edit' selected, clicking on the RTE link inputbox in the modal window caused the grid row to be submitted as if the click took place outside the grid. The gridEventHandler has been updated to correct this.
SR-B9916 · Issue 283675
Hyperlink works on custom HC login page
Resolved in Pega Version 7.3
In a Hybrid Client App with a custom login page, a simple HTML link which calls the function to load the mashup code for the gadget worked in the browser but not in the HC. This was caused by window.open not working inside HC. To enable this, the _launchPopup api of compositegadgetmgr.js has been modified to use launchbox.Browser.start instead of window.open and the isCookieConsentRequired API has been updated to return false for popup case.
INC-127981 · Issue 562998
Rulesets removed from direct invocation ability
Resolved in Pega Version 8.2.7
The following rules have been updated such that they are no longer available to be invoked directly by a client or service: Clipboard_ExecuteActivity, getClassInstances, getOperatorIDs, and GetXMLRuleData. In addition, pzAutoGenClipboard_ExecuteActivity will now require authentication.
SR-D79831 · Issue 562800
Access Deny working as expected for Offers
Resolved in Pega Version 8.2.7
It was possible to Save-As an offer in PegaMKT-Work-Offer after encountering an access deny rule. The record was not created in Dev Studio, however, and an expected denial of access was not registered at runtime. This was due to Access deny rules not being considered as a part of validation, and has been resolved by adding the necessary permission validation to the new harness that will produce the error message informing the user that they are missing a permission. Additional work has also been done to pass the 'pzKeepPageMessages' parameter as true so that page level error messages are correctly displayed.
SR-D87673 · Issue 548627
PegaCESvcsIntegrator security updated
Resolved in Pega Version 8.2.7
Security updates have been made which now require authentication to consume the services from the PegaCESvcsIntegrator package.
SR-D88451 · Issue 550848
Testcases are not available for 'access when' rules
Resolved in Pega Version 8.2.7
Attempting to create test cases for access when rules resulted in guardrail warnings about the need to create a test case. Because Test Cases are not available for the Access When rule type as per Pega expected behavior, the guardrail warnings are not valid and have been removed.
SR-D91834 · Issue 554424
Related cases of different types properly linked in Case Worker Portal
Resolved in Pega Version 8.2.7
After creating a case of type1 in the Case Worker portal, creating a case of type2 from the first case showed the case ID of the second case in the Related Work section as expected. However, after clicking on the link of the case ID of the second case from the related work section, the second case opened but the case ID of the first case was not shown in the Related work. The cases were correctly associated when the Case Manager portal was used instead. This was traced to the Case Worker clipboard continuing to hold the previous case ID thread, and has been resolved.