INC-215354 · Issue 712666
Data- flow actions working in Bulk Process
Resolved in Pega Version 8.8
When trying to render a flow action whose 'applies to' class was inherited from Data-, an error was generated indicating that the flow action could not be found. This was traced to non Work- flow actions not being correctly populated, and was an inadvertent side effect of work done to set class for inheritance if Work- is not present. This has been resolved by updating the pzPreBulkProcessModal activity to set the TempWorkPage class to Work- only if .pyActionName is pyTransferAssignment.
INC-215499 · Issue 714488
Assignment routing updated for swimlanes
Resolved in Pega Version 8.8
Routing options were not working for workbasket routing when using swimlanes. Investigation showed that when an assignment was added inside the swimlane, the assignment type value was defaulting to Worklist on submit of the assignment property panel. Manually changing it to workqueue did not make the routing section visible. This has been resolved by adding a 'visible when' condition to the "Route To" field to check if the assignment is not in the swimlane. The same check has been added to a 'disable when' condition for the 'Assignment type' drop down.
INC-216406 · Issue 723286
Attachment preview works for filenames with special characters
Resolved in Pega Version 8.8
Attempting to preview attachments from the file and attachments view was not working if the file name had special characters. The browser console showed errors complaining that an unrecognized character was present. This has been resolved by adding crossScriptingFilter to sMemo to allow special characters in the attachment preview filename.
INC-222388 · Issue 731651
Handling updated for custom flow bulk actions
Resolved in Pega Version 8.8
If the first assignment in a bulk queue failed validation of the flow action, the other selected assignments with same validations also failed without going to queue. This occurred when custom flow actions were configured on the standard bulk processing section, and caused the incorrect email template to be sent. To resolve this, Activity ProcessMultipleAssignments has been modified to add jump conditions to address the errors in PerformFlowAction and handle exception scenarios and ensure the proper template is sent.
INC-224299 · Issue 736466
CaseTypeClass property created in @baseclass for better upgrade compatibility
Resolved in Pega Version 8.8
When trying to use page-validate on pyWorkPage the error "The page contains an undefined property: pyWorkPage.pyAddableWorkList(1).caseTypeClass\nValidation failed: Errors Detected" was generated. This was traced to the difference in handling for old casetypes from earlier versions of Pega, and has been resolved by creating the caseTypeClass property in @baseclass.
INC-224548 · Issue 725323
Case Wide Actions do not trigger assignment arrow mark to progress
Resolved in Pega Version 8.8
Given a case type with two assignments in first stage, if the first assignment is completed and then a case-wide action is performed before beginning the second assignment, the the chevron arrow mark was shown pointing to the second assignment even though the user was performing a case-wide action. This was traced to the activity pzLoadStageStatusDP step 10 java step where pxFlow page is taken from the pyWorkPage and the pyLastFlowStep property holds the next step that will be performed. As pxFlow holds the flow parameters of current flow being performed, pxIsCurrent ends up set on the wrong step. To resolve this, a "when" condition has been added in the pyStageStepList section for the arrow mark to be visible only if it is not case-wide local action.
INC-224726 · Issue 730543
Resolved drag and drop duplicate entries
Resolved in Pega Version 8.8
Including files with Drag and Drop control was resulting in duplicate file entries. This was traced to run visibility on client being enabled by default on layout in the section pzAttachContentScreen, and has been resolved by modifying the default to be that run visibility on client is disabled on layout in this section when pyDescription is null.
INC-226400 · Issue 731712
Adhoc case creation repaired
Resolved in Pega Version 8.8
Adhoc case creation was not working. The adhoc case creation flow action uses a page called "newWorkPage" for case creation: this parameter page which is used by the pySaveAdHocCase activity in the pyCreateAdhocCase flow action has a naming conflict with page name in activity pzShowConflicts, resulting in the system removing both the pages in step 11 of pzShowConflicts activity. To resolve this, the page created and used in pzShowConflicts has been renamed from newWorkPage to showConflictsWorkPage.
INC-228513 · Issue 736683
Operator ID recorded in pxStageHistory
Resolved in Pega Version 8.8
In order to support capturing, reporting, and extracting the operator ID of the users starting and completing the stages and steps in the case lifecycle, an update has been made which will store the operator ID in pxStageHistory.
INC-230662 · Issue 738959
Security updated for AttachmentInnerDetails
Resolved in Pega Version 8.8
Cross-site scripting protections have been updated for AttachmentInnerDetails.