INC-173953 · Issue 650852
Updated Pega DX API special character handling
Resolved in Pega Version 8.7
When the using Pega API v1 and invoking api/v1/cases/{ID}/actions/{actionID} for a few fields in section, special characters were being converted into HTML entities. For example,"You'll usually find this information in your terms and conditions." was being converted as "You& #39;ll usually find this information in your terms and conditions" in the API response. This has been resolved by updating the system to ensure the pyDXAPIEncodeValues application setting is honored.
SR-121632 · Issue 183997
RefreshOnConflicts changed for better locking
Resolved in Pega Version 7.1.8
During work flow processing, using the Out-Of-The-Box "Refresh" action and then submitting the current assignment removed the ability to submit the following assignment and an error was generated: "You have lost the ability to make this change because a change elsewhere has taken precedence over the change you made here. Please click on the assignment again to continue." If there are back-to-back assignments and the 'Refresh on Other' action is clicked first, when the second assignment is submitted this lost locking error is displayed. To resolve this, the RefreshOnConflicts activity has been changed to invoke ProcessAssignment on newAssignPage instead of WorkPage so that the locking mechanism will function as expected.
INC-184816 · Issue 674433
Added handling to find the workparty for FixCorrespondence
Resolved in Pega Version 8.7
Using a Send Email smart shape and triggering email by passing the target email ID instead of the workparty role triggered the email as expected, but if a fix correspondence flow was initiated due to some error during the transaction, it was not possible to resubmit the fix flow action. Investigation showed that this was due to the fix correspondence flow check using the party role, which had not been passed. This has been resolved by updating the corrUpdate and createAndProcessCorr activities to copy the pyCorrPage from NotifyOp which contains the getgetEmailSenderInfo and use it to set pyCorrPage.pyStreamType.
SR-123245 · Issue 185467
Resolved frame stack error with Flow GenerateAndProcessRequirements
Resolved in Pega Version 7.1.8
Flow GenerateAndProcessRequirements had an error in step Utility2 that generated a Frame stack error. This was caused by the method used for ClipboardObjectImpl.getThread(): in the case when owning thread is from a different requestor, it is possible that two requestors are simultaneously executing on the owning thread. In this case, the PRStackFrame push pop calls from both the requestors (foreground browser requestor and background declare trigger activity requestor) interfered with each other and caused the error. This has been fixed. / UpdateOpenCoveredTasks was causing null pointer exception due to the trigger activity, 'Work-Cover-. UpdateOpenCoveredTasks' not being available to this activity - the trigger is defined to run in background. Exceptions are thrown because the system was checking for messages on tempWorkPage page and tempWorkPage was being deleted in few cases. To fix this, a condition has been added to check whether tempWorkPage exists before checking for messages on it.
SR-123245 · Issue 185150
Resolved frame stack error with Flow GenerateAndProcessRequirements
Resolved in Pega Version 7.1.8
Flow GenerateAndProcessRequirements had an error in step Utility2 that generated a Frame stack error. This was caused by the method used for ClipboardObjectImpl.getThread(): in the case when owning thread is from a different requestor, it is possible that two requestors are simultaneously executing on the owning thread. In this case, the PRStackFrame push pop calls from both the requestors (foreground browser requestor and background declare trigger activity requestor) interfered with each other and caused the error. This has been fixed. / UpdateOpenCoveredTasks was causing null pointer exception due to the trigger activity, 'Work-Cover-. UpdateOpenCoveredTasks' not being available to this activity - the trigger is defined to run in background. Exceptions are thrown because the system was checking for messages on tempWorkPage page and tempWorkPage was being deleted in few cases. To fix this, a condition has been added to check whether tempWorkPage exists before checking for messages on it.
INC-172584 · Issue 654924
Deprecated NewWorkGadget registered for BAC
Resolved in Pega Version 8.7
Logging in through the Administrator portal and launching a new project resulted in a blank screen. Investigation traced this to the Create New Work action called in the NewWorkGadget control; because the NewWorkGadget is no longer used by Pega, it was not registered for use with BAC. To resolve this, validations have been added for Control: NewWorkGadget, and the control has been marked as deprecated.
INC-189622 · Issue 682098
Cleaned up references to deprecated property type
Resolved in Pega Version 8.7
While using the Pega API to update a case from one application to another, an error was generated indicating the system was unable to find a property definition of “caseTypeClass” in pyAddableWorkList of the workpage. All properties in the clipboard pages of the work page are validated during this update: in this case, the check was for the caseTypeClass property, which is no longer used but which was on the clipboard page. To resolve this error, all remaining references to property casetypeclass have been removed.
SR-122504 · Issue 189293
Made operator identification consistent across flows
Resolved in Pega Version 7.1.8
A naming difference was seen in work flows depending on whether Visio or modular functions were used: Visio picks the "Task_Assignment2" function to generate java for assignment, giving the operator ID, but modular flows use "Task_Assignment" and show the operator name. In order to show consistent behavior, the code has been modified such that it first gets the operator name from the assign page if it exists, and it does not exist it will fall back to sending the operator ID as parameter.
INC-175762 · Issue 669398
BulkProcess harness deprecated in favor of BulkProcessing
Resolved in Pega Version 8.7
The harness pzBulkProcess has been marked as deprecated. In place of this, implement the new Bulk Action functionality available using the harness pzBulkProcessing.
SR-120586 · Issue 179198
Assignment dependencies with child cases now properly resolve
Resolved in Pega Version 7.1.8
Using a dependency on an assignment based on a child case can case an error. This was due to the obj class being wrongly populated, and has been resolved.