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-102005 · Issue 556731

Child case ID prefix preserved

Resolved in Pega Version 8.4.2

When configuring a case as a child case in App Studio, the case ID prefix was cleared out of the field on the Settings tab for the case type. Investigation showed that when the child case was added to the parent case in App studio, pzaddcasetypetoapp was called but the parent activities did not pass the CaseID parameter of the child case type. This caused the CaseID prefix of the child to be null and displayed as blank in the Settings and Application. This has been corrected by ensuring the system will get and set the parameter value.

INC-119754 · Issue 561523

Corrected 'when' rule context for GetCaseDetails

Resolved in Pega Version 8.4.2

The Pega REST API Get Method /cases{CaseID} failed if the Child Case was set with Manual instantiation using a 'when' rule. This was traced to the 'when' rule being resolved using @baseclass instead of the class of the case type, and has been resolved by updating the pzGetCaseDetails activity to evaluate the 'when' rule on the case page.

INC-120608 · Issue 573001

Temporary case creation from Cosmos resolved

Resolved in Pega Version 8.4.2

Creating a temporary case in Cosmos Portal was not working. Investigation showed that the pySkipCreateHarness and pyCreatesTemporaryObject properties were not populating properly on the D_StartingFlows data page, which was traced to the way openSelectedColumns API handles non-exposed columns. To resolve this, the system has been updated to use the openEngine API for opening starting flows if the pySkipNewHarness or pyCreatesTemporaryObject property values are null.

INC-121435 · Issue 563877

Handling added for null requiredskillcount on assignment

Resolved in Pega Version 8.4.2

If the property pxRequiredSkillCount was blank on an assignment when moved to a workbasket, it was never presented for Get Next Work. To resolve this, handling has been added which will change the null to 0 so the assignment is properly queued.

INC-127077 · Issue 564109

Busy indicator appears when uploading via Select

Resolved in Pega Version 8.4.2

After upgrade, the “loading symbol” (busy indicator) was not appearing while uploading large attachments using the Select button. This was a missed use case in recent changes to related to AsyncUpload, and has been resolved.

INC-128087 · Issue 572452

Temporary case creation from Cosmos resolved

Resolved in Pega Version 8.4.2

Creating a temporary case in Cosmos Portal was not working. Investigation showed that the pySkipCreateHarness and pyCreatesTemporaryObject properties were not populating properly on the D_StartingFlows data page, which was traced to the way openSelectedColumns API handles non-exposed columns. To resolve this, the system has been updated to use the openEngine API for opening starting flows if the pySkipNewHarness or pyCreatesTemporaryObject property values are null.

INC-128921 · Issue 571866

Updated End User portal Cross-site scripting handling

Resolved in Pega Version 8.4.2

Additional Cross-site scripting handling has been added to the End User portal.

INC-129982 · Issue 574393

Temporary case creation from Cosmos resolved

Resolved in Pega Version 8.4.2

Creating a temporary case in Cosmos Portal was not working. Investigation showed that the pySkipCreateHarness and pyCreatesTemporaryObject properties were not populating properly on the D_StartingFlows data page, which was traced to the way openSelectedColumns API handles non-exposed columns. To resolve this, the system has been updated to use the openEngine API for opening starting flows if the pySkipNewHarness or pyCreatesTemporaryObject property values are null.

INC-130326 · Issue 571522

Added handling for apostrophe in Pulse username

Resolved in Pega Version 8.4.2

The User Name in Pulse notifications was displayed with symbols if the username has special characters in it, for example the apostrophe in "O'Hara" was showing as ' in any notification. This was a side effect of work done to improve security, and has been resolved by using org.apache.commons.lang.StringEscapeUtils.unescapeHtml to unescape HTML characters in the pzDisplayGadgetMessage control.

INC-131025 · Issue 573113

CheckStorageForDuplicateFiles validation added

Resolved in Pega Version 8.4.2

When two files were attached to case, attempting to delete one file and download the other one resulted in the error "Unable to get file from repository. There was a problem setting/connecting the file path or repository”, and an exception related to "There was an issue creating stream for the file.: Cannot find S3 object at Container" was generated. As repositories are not allowing file versioning, validation was not happening when multiple files with the same file name were uploaded. To resolve this, an enhancement has been made to perform validation in the pzCheckStorageForDuplicateFiles activity.

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