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-160078 · Issue 628839

Work object status correctly set to Resolved after refresh

Resolved in Pega Version 8.6

When using the Refresh option from the Other Actions menu before submitting the flow action, the work object status was not updating to Resolved-Completed. Investigation showed that when performing the Refresh action, the RefreshOnConflicts activity created a Clipboard page named LatestWorkPage with a copy of the work object. This page was not removed after use, causing the Resolved-Completed status to be set on LatestWorkPage instead of pyWorkPage. To resolve this, a step has been added to RefreshOnConflicts to remove LatestWorkPage.

INC-160115 · Issue 627650

Editing Approval flowshape retains decision tree

Resolved in Pega Version 8.6

Editing the Approval flowshape caused the decision tree to become blank when selecting 'Use Business logic' in the dropdown for "Route to dropdown". This was traced to a missed use case for earlier work done on enhancements for email approver shapes regarding retaining previous values while switching back to using the business logic option, and has been resolved.

INC-162550 · Issue 630274

RefreshFor correctly returns validation messages

Resolved in Pega Version 8.6

After upgrade, the PUT method on /api/v1/assignments/{ID}/actions/{actionID}/refresh?refreshFor was not returning validation messages on the child level. This was an unintended consequence of refactoring work done on pzApiCreateJsonForField around the default value calculation, and has been resolved. In addition, an issue with read-only text controls not being localized has been corrected.

INC-164413 · Issue 636126

Updated timestamp handling for duplicate key issue with PyCompleteAutomation

Resolved in Pega Version 8.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.

SR-SR-D60505 · Issue 522998

Upload with "Select File" works in Microsoft Internet Explorer

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.

INC-161463 · Issue 638002

Case Dependency corrected for different access groups

Resolved in Pega Version 8.5.4

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-161948 · Issue 638962

Locking settings enabled for circumstanced case types

Resolved in Pega Version 8.5.4

Optimistic locking options were not present for a circumstanced case type, and the option to select the "Lock parent case when an action is performed on this case" check box was not available. However, when the parent case type was enabled with optimistic locking, a circumstanced child case could inherit a lock from its parent. Because "Lock parent case when an action is performed on this case" was not enabled on the circumstanced child case type, trying to update the parent case from the child case and save the parent case resulted in a "Lock not held on parent" error. This was a missed use case, and has been resolved by enabling locking settings in Case Designer for circumstanced case types.

INC-162168 · Issue 634934

Refresh works for nested lists

Resolved in Pega Version 8.5.4

After creating Pagelist A with another Pagelist within (B), a section was created with a repeating dynamic layout to display Pagelist A and a button was added with action set to refresh this section. In the embedded section of the repeating dynamic layout, a nested repeating dynamic layout was created for Pagelist B and a button was set to refresh this section. When using this configuration, the refresh was returning the actionID for Pagelist A regardless of which button was used. To resolve this, an update has been made which will iterate over the stack and append the individual indexes to the encoded value in the pzAPICreateJsonForField function.

INC-162550 · Issue 630273

Read-only text controls properly localized

Resolved in Pega Version 8.5.4

An issue with localization of property references used in read-only text controls when calling dx api v1 /assignments/{ID}/actions/{ID} in context of DataGather application in attachment JSON response has been corrected.

INC-162763 · Issue 646110

Case creation and Save As performance improvements

Resolved in Pega Version 8.5.4

Performance improvements have been made to the getApplicationRuleSetList() function to avoid unnecessary and repetitive database calls.

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