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-132297 · Issue 583956

FlowAction HelpText retained on refresh

Resolved in Pega Version 8.5.1

When a FlowAction configured with HTML was rendered on UI, reloading made the HelpText disappear. Flow action help icon is displayed using pzActionHelp control, which uses the Task Index parameter to determine whether to show the help icon or not. Investigation showed that when pyCaseActionAreaHeader was getting refreshed, this parameter was missed. To resolve this, the pzActionHelp control has been modified to fetch the correct action and index which will be used in displaying the flow action help.

INC-135751 · Issue 587287

Null check added for embedded section pyInclude tag

Resolved in Pega Version 8.5.1

When attempting to implement a call to the Pega API casetypes endpoint, the end point /casetypes/{id} returned data for only some of the casetype IDs. For others there was no content in the response and in the logs the error "null at com.pegarules.generated.pzAPICreateJsonForGroup" was seen. This was traced to the use of an old section which did not generate the embedded section pyInclude tag. When the API was called on the same section, it tried to perform an equality check on the variable which gets the pyInclude value, and the null value caused the null-pointer exception. This has been resolved by adding a null check to cover pyInclude in an embedded section.

INC-129443 · Issue 582612

Reopen details correctly saved to pxResolveSummary

Resolved in Pega Version 8.5.1

When cases were reopened using a call to the out-of-the-box Work-.Reopen activity or the Re-open work item link in the Case Tools, the changes to track the reopen in pxResolveSummary were not saved and were lost after a refresh of the case. This has been resolved by updating the ticket handling and modifying the reopenworkobject activity to set the resolve-summary details before re-opening the WO.

INC-129533 · Issue 576661

Proper MIME type kept for attachments

Resolved in Pega Version 8.5.1

When Email Listeners processed an email with an attachment and stored that attachment to an instance of DATA-WORKATTACH-FILE, it did not keep the full MIME type in the property pyAttachMimeType, but kept just the subtype (so "application/PDF" became "PDF" and "image/jpeg" became "jpeg"). As a consequence, the MIME type could not be reconstructed correctly when the file was attached to an outbound email. While most email clients were able to reconstruct (guess) the type of the file from the filename (or, more precisely, from the extension), this did not work when the email was processed by an automated system reliant on the correctly set Content-Type header. This has been corrected by reading the mime type from data-workattach-file page and setting the content type header while constructing the multipart with this value.

INC-128193 · Issue 575947

Added check for OperatorID page

Resolved in Pega Version 8.5.1

When logging in, operators were seeing exceptions related to "reference .pxOperatorSkillsCount is not valid. Reason: FUAInstance-NullMyStepPage at com.pegarules.generated.activity.ra_action_setworkinfo". The OperatorID page is created when a user is logged in, and the scenario of an OperatorID page not being present is rare but can occur. To resolve this, a 'when' condition has been added to check whether the OperatorID page exists before populating the pxOperatorSkillCount property.

INC-135161 · Issue 580936

Upload with "Select File" works in IE

Resolved in Pega Version 8.5.1

When using IE, uploading a document was failing on the first try when using the "Select File" button. The second attempt worked as expected. This was an intended consequence of work done to enable attaching the same file after deleting it, and was related to Microsoft 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-136206 · Issue 584327

Handling added for Japanese characters in filename during Safari file upload

Resolved in Pega Version 8.5.1

When using the Safari browser, uploading a file containing Japanese characters resulted in an error message indicating the file was not found afterwards. This was caused by Safari not encoding the flename in the Form Data/Query String as part of the request for file upload, resulting in the filename not being decoded properly. To resolve this, a function named pzBrowserIsSafari has been added to check the browser, and if it is Safari, the system will normalize the filename.

INC-139074 · Issue 587811

Email handling security updated

Resolved in Pega Version 8.5.1

Cross-site scripting protections have been enhanced for email activities.

SR-D98224 · Issue 580594

Updated endpoint Cross-site scripting protection

Resolved in Pega Version 8.5.1

Cross-site scripting security has been updated for Endpoints in Display activities.

INC-134709 · Issue 579438

Updated endpoint Cross-site scripting protection

Resolved in Pega Version 8.5.1

Cross-site scripting security has been updated for Endpoints in Display activities.

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