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-146564 · Issue 607857

DX API returns application specific validation messages

Resolved in Pega Version 8.6

When trying to validate the input swagger details with application specific conditions, the create case DX API did not return the validation messages from application but instead returned a "500 Internal Server Error". Investigation showed that the error parameter was not set on validation fail, and this has been corrected.

INC-146780 · Issue 602024

Updated ArchivedCaseHistory visibility

Resolved in Pega Version 8.6

After enabling case archiving on Pega Cloud, it was possible to search the cases from case manager studio, but the audit details were missing. Previously Audit History was directly displayed based on whether archival was enabled or not. As part of Field Level Audit, a new property called pyHistoryViewType was introduced which is a prompt list with ALL and FIELD as its values. This property checks whether FLA is enabled or not, and based on that value ALL is set. In this case, because FLA was not enabled, the pyHistoryViewType property was empty and the HISTORY tab was not shown. To resolve this, the pyArchivedCaseHistory section table 2 visibility condition has been updated.

INC-147457 · Issue 621710

Elapsed time in Work History Table includes sub-flow

Resolved in Pega Version 8.6

Elapsed times were not captured when an assignment was in a wait shape followed by a utility which set a ticket and moved the assignment to a sub-flow. Investigation showed that when flow execution is in a sub-flow and a ticket is raised, the assignment in sub-flow was removed but audit history was not captured. To handle this scenario, the functions pzCleanSplitForTicket and pzRemoveFlowForTicket have been added, and FlowMethodBody FUA has been modified to include pzCleanSplitForTicket instead of CleanSplit.

INC-147658 · Issue 604685

Handling added for Top and Primary page references in flow action

Resolved in Pega Version 8.6

After upgrade, if a flow action had a class of the section which was different from the class of the flow action, the DXAPI code retrieved the section as the same class of the flow action and not the class defined in the flow action. In flow action, the section was configured be rendered in the context of page reference as Top, however, this was not handled so the section was resolved in the context of primary page. This has been resolved by adding the missing handling for Top and Primary page references in flow action.

INC-148747 · Issue 613877

Helper text set for radio buttons in DX API

Resolved in Pega Version 8.6

The api/v1/assignments/{ID}/actions/{actionID} Service Rest was not rendering the tooltip into DXAPI converted JSON for Radio Button Helper Text. This was traced to a missing Tooltip check in the API Rule-Utility-Function for radio buttons, and has been resolved.

INC-148817 · Issue 604970

Added check for ABAC policy to getassignmentdetailsinternal

Resolved in Pega Version 8.6

When an attribute based access control (ABAC) policy was defined on a particular class, the policy was properly applied when browsing instances of the class and directly opening the work object. However when an associated assignment was processed via the DXAPI (using the assignments service) the security was not applied and users who should not have access were able to progress the case. This has been resolved by adding a check in the pzgetassignmentdetailsinternal activity to check for work object opening security.

INC-149213 · Issue 608518

Email attachments properly displayed in mobile browsers

Resolved in Pega Version 8.6

When attempting to use any mobile browser to open the email attachment of a work object, a blank HTML page appeared before the email attachment was shown. The blank page did not appear if the mobile browser was set to use "Desktop mode" or "PC mode". This has been resolved by updating the BAC registration method so that correspondence attachments are properly opened in all mobile browsers and HC apps for all channel types. An additional issue of a blank window appearing on IOS devices that was caused by correspondence attachments opening in a new window instead of opening in the current window has also been corrected.

INC-149823 · Issue 608353

DX API returns properly referenced icon class for embedded page

Resolved in Pega Version 8.6

When using the DX API to build an Angular JS UI, the response returned from the GET /cases/{ID}/actions/{actionID} api did not return the iconStyle for an icon class that uses a property reference when the flow is on an embedded page. This has been resolved by adding code to set the correct context for pzAPICreateJsonForModes and pzAPICreateJsonForField RUF.

INC-149946 · Issue 609042

OpenIfStale updated to resolve optimistic locking race condition

Resolved in Pega Version 8.6

A race condition was created in optimistic locking by having two assignments save at overlapping times. This has been resolved by modifying the pzShowConflicts activity to use a version of openIfStale which will consider a workpage as stale even if the difference in pxUpdateDatetime is in milliseconds.

INC-149988 · Issue 608821

Upload with "Select File" works in Microsoft IE

Resolved in Pega Version 8.6

When using Microsoft Internet Explorer, uploading a document was failing on the first try when using the "Select File" button. The second attempt worked as expected. This was an unintended consequence of work done to enable attaching the same file after deleting it, and was related to Internet Explorer calling an "onChange" which caused the "pzAttachFileDDFileList" section which is used to display the attachments uploaded to not be properly refreshed. This has been resolved by updating the pzMultiFilePath control handling of the success and failure of the upload function call.

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