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.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-173725 · Issue 656480

Logic updated for DX API retrieving View/Action ID using embedded property

Resolved in Pega Version 8.7

While calling the DX API using Assignment ID and action ID, a 500 error response was logged indicating that the server encountered an unexpected condition that prevented it from fulfilling the request. Investigation traced this to the logic used for resolving an embedded property referenced in a control/field to identify the correct page class. In a non-work object context for flow actions the new assign page doesn't exist, but the system was checking for it and clearing off errors from the named page. This has been corrected.

INC-170514 · Issue 653762

Lock conflict resolved for AssignmentCheck

Resolved in Pega Version 8.7

The error "Unable to unlock this work object" sporadically appeared in both the runtime log and Pega RULES log when the robot was trying to create a case in Pega using an API call. Investigation showed that as the case was created, it was pulled by another robot (another requestor) which was using the GetAssignments API. This caused the perform assignment check to fail. To resolve this, a 'when' rule has been added to the performAssignmentCheck Activity.

INC-177665 · Issue 662020

Security updated to allow Access group switching

Resolved in Pega Version 8.7

When a member of two different access groups attempted to switch from one group to another, an "access denied" message occurred. This was traced to the use of BAC, and has been resolved by updating the pzProcessApplicationSwitch activity to use the pzEncryptURLActionString function to register the request.

INC-186868 · Issue 675245

Security updated to allow Access group switching

Resolved in Pega Version 8.7

When a member of two different access groups attempted to switch from one group to another, an "access denied" message occurred. This was traced to the use of BAC, and has been resolved by updating the pzProcessApplicationSwitch activity to use the pzEncryptURLActionString function to register the request.

SR-A92126 · Issue 261816

Bulk Action transfers all selected records

Resolved in Pega Version 7.2.2

Not all of the selected cases were being transferred when using the Bulk Actions functionality to transfer. This was due to the pySelected values to not being updated in the clipboard. To resolve this, a Refresh other section has been added to Select Action in pzBulkProcessingActionSection to update the value when clicked.

INC-186654 · Issue 669115

GetStatusChanges performance improvements

Resolved in Pega Version 8.7

Performance issues were seen when running the GetStatusChanges report. This was traced to the filtering methods used, and has been resolved by updating the report definition and enhancing the filtering conditions.

SR-A88385 · Issue 257722

Thumbnail images consistently displayed in overlay

Resolved in Pega Version 7.2.2

When thumbnails were configured with the control pzAttachmentThumbnail), the overlay showed the image differently based on the location of the thumbnail in the screen, for example one side displaying with a scroll bar while the other did not. The earlier design was purely based on non-autogenerated code using a PopOver API call, which couldn't honor the position of the overlay. To resolve this, the Attach Field configuration has been modified so that all the Thumbnail overlays are shown using Local Action and thumbnails will be shown using autogenerated pxIcon control.

INC-186036 · Issue 685371

Field Level Audit updated to handle hierarchical properties

Resolved in Pega Version 8.6.3

Field Audit was not working for the first change of the data selected/provided for a field. The audit was only reflected after the second change was made. When the property involved a series of hierarchies, for example pageprop.pagelist(1).pageprop, the FLA objects will initially use deferred saves and the generated pzinskeys will be added to a savedFLAMap object. However, when the last pageprop was not eligible to save, all the deferred saves of earlier records were cancelled but the inskeys were not removed from the savedFLAMap object. Because of this, the parent FLA records were assumed to have been saved already when those saves were actually deferred. This was a missed use case for hierarchical properties, and has been resolved by adding an update to remove the inskeys from the savedFLAMap object so that in the subsequent property change the audit's FLA records for the parent properties (pageprop.pagelist(1)) will be saved again.

SR-A86522 · Issue 266946

ResumeFlow updated to handle SLA update in batch mode

Resolved in Pega Version 7.2.2

When any assignment configured with SLA was resumed by any agent in batch mode, the associated record in the pr_sys_queue_sla table was not getting deleted. To resolve this, the deletion method used in CompleteAssignment has been updated.

SR-A97665 · Issue 265978

ResumeFlow updated to handle SLA update in batch mode

Resolved in Pega Version 7.2.2

When any assignment configured with SLA was resumed by any agent in batch mode, the associated record in the pr_sys_queue_sla table was not getting deleted. To resolve this, the deletion method used in CompleteAssignment has been updated.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us