Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

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.

SR-117083 · Issue 176581

Added sorting and filtering to work item AssignedTo and Status fields

Resolved in Pega Version 7.1.9

An enhancement has been added to allow for filtering and sorting the list of assignments at the bottom of a work item by the 'Assigned To' and 'Status' fields.

SR-128383 · Issue 193256

Child class assignments carried for bulk processing

Resolved in Pega Version 7.1.9

While processing the assignments from the Bulk Actions, the class of the parent work object was applied to child class assignments. This generated a 'Flow Action not found' error. This has been corrected so when the flow action sets a property value, it is setting the value at pyWorkPage instead of the page list item while processing the Child class assignments.

SR-130216 · Issue 202688

AssignActions modified to correctly ResumeFlow from sub-user

Resolved in Pega Version 7.1.9

If two flow actions were defined on a particular assignment in a flow that used WHEN rules to affect visibility in a sub-user's workflow, ResumeFlow was not correctly picking up the flow after the sub-user performed an action and closed the workflow. This was caused by the AssignActions state persisting instead of repopulating and continuing the flow, and the RUF 'FindAssignment2' has been modified to handle this correctly.

SR-132494 · Issue 201073

Exposed 'style' parameters for Workbasket and Operator dropdowns

Resolved in Pega Version 7.1.9

The ShowAllOperators and WorkBasketGadget out-of-the-box controls defaulted to in-line styles even when alternate styles were provided. To correct this, 'style' is now an exposed parameter for both Workbasket and Operator dropdowns.

SR-132896 · Issue 202844

Added handling for customized flows using "different work item" subprocess

Resolved in Pega Version 7.1.9

After upgrade, customized flows using the "different work item" choice on the subprocess for calling work flow from embedded data page work objects generated the error "'On Another Work Item' was specified yet the same object was supplied." This was traced to a missing pzInsKey for this use case, and the LaunchFlow RUF has been updated to handle this customization.

SR-133048 · Issue 202946

Enhancement added to filter list of bulk processing operators

Resolved in Pega Version 7.1.9

When opening Case Manger portal > Open bulk Actions, selecting the Filter condition as 'Assigned To Operator' showed all operators in the autocomplete list. An enhancement has been added to create the extension activity 'pyGetListOfOperators' for RD which can be updated as per the user requirement to filter the list of operators to be shown in the Bulk Processing Search.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us