INC-161463 · Issue 638000
Case Dependency corrected for different access groups
Resolved in Pega Version 8.3.6
Creating a queue item as part of the case dependency was not working as expected when the access groups of the dependent cases were different. Investigation showed that in this scenario, the logic was looping differently and the DependencyList page in pxCheckFlowDependencies was getting removed. To resolve this, the DependencyList page has been moved so it is processed inside the DependencyList.pxResults loop.
INC-163154 · Issue 638097
Code updated for bulk actions buttons
Resolved in Pega Version 8.3.6
After upgrade, hovering over the "Filter case" button in pzBullkUpdate and the "Create" and "Clear" buttons in pzBulkAddActions caused them to disappear. The warning "This button generates markup that was used to support the older browsers. It is recommended that you update it to the newer markup" was shown, and an update code button appeared. Some custom rules exhibited the same behavior initially, but worked as expected after updating the code and saving them. This has been resolved by updating the buttons in pzBulkUpdate and pzAddBulkActions with the latest UI technologies used for button control codes.
INC-164413 · Issue 636125
Updated timestamp handling for duplicate key issue with PyCompleteAutomation
Resolved in Pega Version 8.3.6
Occasionally a robot failed to complete a case due to a duplicate key exception. This was an issue with the History record creation due to duplicate key erlated to the timestamp, and has been resolved by updating the timestamp handling so that the REST API will use 'getCurrentTimeStampUnique' and for other cases 'pxGetCurrentTimeStampThreadUnique' will be used.
INC-172485 · Issue 649053
Check added for WorkParty property to catch changes
Resolved in Pega Version 8.3.6
After configuring a send email shape to send email to work parties, proceeding through the flow without work parties and then triggering the send email shape and creating the Fix correspondence assignment worked as expected. If the work party details were later updated and the send email shape was triggered again for the Fix correspondence assignment, the error message "No role defined to work object" appeared. This was an issue with the handling of the email flow the second time through: PyCorrPage.pyCorrPartyRole did not have the work object party details which were added to the work object after the fix correspondence assignment was created, and SendSimpleEmail was not designed to handle the email that needs to be retried during the FixCorrespondence flow call. To resolve this, the system will check whether the pyWorkParty property exists prior to calling the PartyCorrPreferences HTML rule.
INC-102005 · Issue 556731
Child case ID prefix preserved
Resolved in Pega Version 8.4.2
When configuring a case as a child case in App Studio, the case ID prefix was cleared out of the field on the Settings tab for the case type. Investigation showed that when the child case was added to the parent case in App studio, pzaddcasetypetoapp was called but the parent activities did not pass the CaseID parameter of the child case type. This caused the CaseID prefix of the child to be null and displayed as blank in the Settings and Application. This has been corrected by ensuring the system will get and set the parameter value.
INC-119754 · Issue 561523
Corrected 'when' rule context for GetCaseDetails
Resolved in Pega Version 8.4.2
The Pega REST API Get Method /cases{CaseID} failed if the Child Case was set with Manual instantiation using a 'when' rule. This was traced to the 'when' rule being resolved using @baseclass instead of the class of the case type, and has been resolved by updating the pzGetCaseDetails activity to evaluate the 'when' rule on the case page.
INC-120608 · Issue 573001
Temporary case creation from Cosmos resolved
Resolved in Pega Version 8.4.2
Creating a temporary case in Cosmos Portal was not working. Investigation showed that the pySkipCreateHarness and pyCreatesTemporaryObject properties were not populating properly on the D_StartingFlows data page, which was traced to the way openSelectedColumns API handles non-exposed columns. To resolve this, the system has been updated to use the openEngine API for opening starting flows if the pySkipNewHarness or pyCreatesTemporaryObject property values are null.
INC-121435 · Issue 563877
Handling added for null requiredskillcount on assignment
Resolved in Pega Version 8.4.2
If the property pxRequiredSkillCount was blank on an assignment when moved to a workbasket, it was never presented for Get Next Work. To resolve this, handling has been added which will change the null to 0 so the assignment is properly queued.
INC-127077 · Issue 564109
Busy indicator appears when uploading via Select
Resolved in Pega Version 8.4.2
After upgrade, the “loading symbol” (busy indicator) was not appearing while uploading large attachments using the Select button. This was a missed use case in recent changes to related to AsyncUpload, and has been resolved.
INC-128087 · Issue 572452
Temporary case creation from Cosmos resolved
Resolved in Pega Version 8.4.2
Creating a temporary case in Cosmos Portal was not working. Investigation showed that the pySkipCreateHarness and pyCreatesTemporaryObject properties were not populating properly on the D_StartingFlows data page, which was traced to the way openSelectedColumns API handles non-exposed columns. To resolve this, the system has been updated to use the openEngine API for opening starting flows if the pySkipNewHarness or pyCreatesTemporaryObject property values are null.