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-162894 · Issue 644181

Deleting attachment with icon button works in Attachment section

Resolved in Pega Version 8.5.4

After upgrade, a delete icon in the attachment section was not working as expected. This was traced to BAC work done earlier, and has been resolved by updating the Delete Attachment function of the AttachmentListViewSelectorScript.

INC-163154 · Issue 638099

Code updated for bulk actions buttons

Resolved in Pega Version 8.5.4

After upgrade, hovering over the "Filter case" button in pzBullkUpdate and the "Create" and "Clear" buttons in pzBulkAddActions caused them to disappear. The warning "This button generates markup that was used to support the older browsers. It is recommended that you update it to the newer markup" was shown, and an update code button appeared. Some custom rules exhibited the same behavior initially, but worked as expected after updating the code and saving them. This has been resolved by updating the buttons in pzBulkUpdate and pzAddBulkActions with the latest UI technologies used for button control codes.

INC-165445 · Issue 649150

Corrected case for Location output parameter name

Resolved in Pega Version 8.5.4

The activity pzCreateCaseV2Impl which is used for the create case API was not returning the "location" output parameter due to the parameter being set as "Location", with capital L inside activity pzCreateCaseInternal at step 10. This has been corrected by renaming the parameter 'location' to 'Location'.

INC-166820 · Issue 649968

Blank parameter handling added to assignments function

Resolved in Pega Version 8.5.4

When calling the Pega v1 API /assignments/{ID}/actions/{actionID} a 500 Internal Server Error status was returned if the configuration included an Autocomplete configured with two fields where the second had the "Use in Search" setting enabled. An error was also logged. Once the error occurred, editing the Autocomplete to disable the second "Use in Search" did not stop the error; the entire Autocomplete had to be deleted and recreated. This was traced to the system trying to set a blank parameter due to the autocomplete being configured with a data page with no parameters, and has been resolved by modifying the pzAPIDetermineOptionsFromPage Rule-Utility-Function to not set parameters when the parameter key is blank.

INC-169323 · Issue 646268

Deleting attachment with icon button works in Attachment section

Resolved in Pega Version 8.5.4

After upgrade, a delete icon in the attachment section was not working as expected. This was traced to BAC work done earlier, and has been resolved by updating the Delete Attachment function of the AttachmentListViewSelectorScript.

INC-170041 · Issue 649669

Check and error message added for filename containing "%00"

Resolved in Pega Version 8.5.4

At the time of file attachment or upload, if the file name contained % followed by two 0s (%00), the file upload mechanism distorted the UI and the Pega logo screen popped up. The file was saved properly in the ServiceExport directory, but while fetching the attachment info, the file was split in two because the engine considered %00 as a delimiter. This has been resolved by adding a file name check and a pyInvalidFileName field value to be used for an error message.

INC-173953 · Issue 650851

Updated Pega DX API special character handling

Resolved in Pega Version 8.5.4

When the using Pega API v1 and invoking api/v1/cases/{ID}/actions/{actionID} for a few fields in section, special characters were being converted into HTML entities. For example,"You'll usually find this information in your terms and conditions." was being converted as "You& #39;ll usually find this information in your terms and conditions" in the API response. This has been resolved by updating the system to ensure the pyDXAPIEncodeValues application setting is honored.

INC-174355 · Issue 652051

Corrected file download in Cosmos

Resolved in Pega Version 8.5.4

An unauthorized request error was seen in tracer while downloading files in the Cosmos application. This was traced to the pyAttachmentFeedDescription control in the Theme Cosmos Rule Set not being correctly updated, and has been resolved.

INC-176091 · Issue 652121

Busy indicator correctly resolves with Microsoft Internet Explorer upload

Resolved in Pega Version 8.5.4

When using Microsoft Internet Explorer to upload documents, the busy indicator was not resolving after the file was attached. This was due to a missed use case in work done around the timing of the busy indicator when attaching multiple files, and has been resolved by modifying PzMultiFilePath to ensure the busy Indicator is removed when the file count is zero.

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.

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