SR-D72672 · Issue 536388
Security updated for CreateOperator
Resolved in Pega Version 8.2.6
In order to improve security, CreateOperator in Pega-ProCom will require authentication to run with pxCanManageUsers privilege.
SR-D75469 · Issue 538121
Resolved null-pointer exception in Expression Builder launch from activity rule
Resolved in Pega Version 8.2.6
A NullPointerException occurred in SafeURL when trying to launch the Expression Builder from an activity rule. This was trasced to a failure to get a value property in a target field due to the target element and its parent element containing the same value for name attribute. This caused the parent element to be considered instead of the target element. To resolve this, the search for the target element in parent tag will use '$p' along with 'target element name' in query selector.
SR-D78698 · Issue 545386
Improved temporary page clearing for UpdateAndDeleteAssignments
Resolved in Pega Version 8.2.6
When using the Change Stage shape in a flow to move it to the Complete stage, the expectation is that the status should be set to Resolved-Completed and all open assignments should be deleted. In some scenarios, the audit history showed the case moved to the Complete stage and the assignments deleted properly, but the case status was not set to Resolved-Completed. This was traced to the temporary page "pgWork_x" getting leaked from pzUpdateAndDeleteAssignments activity when a case is being processed to closure (via pzProcessResolutionStage > pxForceCaseClose path). When the same work object was reprocessed in the same thread and the findPageByHandle(WorkObjectID) function received this temporary page's reference, then the actual operation was not committed to the database. To resolve this, updates have been made to remove the precondition at step#15 of the pzUpdateAndDeleteAssignments activity to ensure the temporary page gets removed appropriately.
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.