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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-134113 · Issue 591541

Child case locking error message has correct parameter

Resolved in Pega Version 8.5.2

A locking error message was appearing without the case parameter, showing "Error Message : Could not lock the cover ; has it. Please wait and try again later." This was traced to the cover already being present, causing the step to open the Cover Object to fail. To resolve this, and update has been added to pass the Cover case ID to the field value.

INC-136327 · Issue 591466

Stage keeps proper order placement on restart

Resolved in Pega Version 8.5.2

When a user restarted a stage, the stage moved to the end of the list of stages and stayed there even when completed. Investigation showed that when pxRestartStage was configured as a post-processing activity for a flow action, pxStageHistory was updated with a new list item which considered pxCameFrom and pxStageId as the same. Due to this, the current stage was moved to last in the chevron. This has been resolved by adding a new 'when' condition to pzLoadStageStatusDP that will skip the item of pxStageHistory (Alternate stage) if both .pxCameFrom and .pxStageId are same.

INC-138348 · Issue 599770

Added parameter skipPropertyEvaluation to handle CSS in email HTML

Resolved in Pega Version 8.5.2

While sending an email with custom HTML appended to the email body, a "+" sign in the body was causing the correspondence generation to fail. Investigation showed that if there were CSS classes with braces in the message body, the braces were being removed and replaced via "+" symbol in step 21 of CorrCreate activity. To resolve this, a new Boolean parameter skipPropertyEvaluation has been added in the CorrCreate activity to handle the decision to either evaluate the logic or not, and the pre-requisite will be to resolve all the property references before calling this activity so custom CSS braces { } will be honored when the message body is sent.

INC-141751 · Issue 596136

DragAndDrop attaching large file properly disables 'X'

Resolved in Pega Version 8.5.2

When a large file was attached using the DragAndDrop feature, the 'X' icon/button was not disabled. This made it possible to click 'X' and perform other actions during the upload, which caused the screen to freeze and required a browser refresh to continue the work. This was traced to incomplete work done on large file uploads, and has been resolved by ensuring the busy Indicator shown will be applied to the complete screen to avoid any other actions being performed.

INC-142660 · Issue 595390

Pega API system management launches correctly from Help

Resolved in Pega Version 8.5.2

The Pega System Management API did not work when launched from help window, although other APIs such as Case Management were working fine. This has been resolved by updating the basePath in pzSystemManagementDocumentation.

INC-143861 · Issue 597557

pzIsScalar 'when' rule updated for Value list and Value group

Resolved in Pega Version 8.5.2

When using the GET/Cases/{ID} API to fetch details about a case, an intermittent HTTP 500 error appeared. This was traced to the 'when' condition pzIsScalar being returned as true for the ValueList property types and trying to set the value on the summaryData embedded page. This has been resolved by updating the pzIsScalar 'when' rule to better handle Value list and Value group.

INC-144358 · Issue 601012

Localization added for "Automatically" and "Manually" field values

Resolved in Pega Version 8.5.2

The Dutch translation of "Child case [Case_type] [Case_id] has been [Instantiation_mode] instantiated" used the hard-coded English expression "manually". This has been resolved by adding the "Automatically" and "Manually" field values to localization.

INC-146339 · Issue 600744

ViewID parameter passed as part of DX API response payload for level 5 applications

Resolved in Pega Version 8.5.2

Recent work to not consider production level and always pass 'viewID' parameter as part of DX API response payload was not working for cases where the APIProductionLevel was 5. This was a missed use case based on a condition that remained on the ViewID parameter, and the condition has now been removed.

INC-146564 · Issue 607856

DX API returns application specific validation messages

Resolved in Pega Version 8.5.2

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 602023

Updated ArchivedCaseHistory visibility

Resolved in Pega Version 8.5.2

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.

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