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.
INC-230826 · Issue 733552
Legacy hardcoded WorkPage removed from ReassignAssignment
Resolved in Pega Version 8.8
When there was a child case Task available, attempting to transfer the case caused the system to update the Parent case .pxFlow(CreateTask) instead of the Task case .pxFlow(CreateTask). This was traced to the pyReassignAssignment activity having a legacy hardcoded page pyWorkPage defined, and this hardcoded page has been removed to resolve this issue.
INC-202004 · Issue 692353
Hotfix documentation updated to point to Hotfix Manager page
Resolved in Pega Version 8.8
The readme file attached to hotfix downloads contained an outdated reference to use "PRPC Hotfix Installer on the Update Manager landing page." This has been updated to point to the Hotfix Manager landing page.
INC-205453 · Issue 706569
Pega Keystore supported for hotfix signature verification
Resolved in Pega Version 8.8
In order to support custom trust managers which require an alternate method for supplying the root certificate via a platform trust store, an enhancement has been added to allow Pega Keystore to be used as a hotfix verification source. Detailed information on this can be found in https://docs.pega.com/keeping-current-pega/87/verifying-hotfix-authenticity-using-pega-keystore
INC-208516 · Issue 705098
Patchdate values made unique
Resolved in Pega Version 8.8
The hotfix manager was incorrectly indicating that a previous hotfix was not installed or was partially installed and should be reinstated. This scenario was created during security updates where the missing/incomplete hotfix had been deliberately deleted from the database, and has been resolved by adding an update which will force patchdate to be unique when adding duplicate code resources during tests.