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-127420 · Issue 568438

Requestor details shown in Pr_perf_stats table

Resolved in Pega Version 8.3.5

When using a Custom table with the requestor details inserted in the ApplicationSetup activity, comparing the passivated requestors from standard table Pr_perf_stats showed that sometimes requestor details were not present in table Pr_perf_stats. This was traced to the the column value for standard table being greater than the column value for the columns pxDecryptCount, pxDecryptCPU, pxDecryptElapsed, pxEncryptElapsed, pxEncryptCPU, and pxEncryptCount. Database numeric column size is (9,6) whereas other numeric columns have size (18,6). To resolve this, the table scripts have been modified to increase the column size from (9,6) to (18,6).

INC-146057 · Issue 599808

Secure access for Activitie

Resolved in Pega Version 8.3.5

Authentication requirements have been added to Standard activities.

INC-128250 · Issue 571240

Validations and rules tuning

Resolved in Pega Version 8.3.5

Issues relating to an extra row being added to auto-populated properties, adding a 'when' visibility to a picklist property, and errors saving nested properties have been resolved, and performance of the overall system has been improved.

INC-137235 · Issue 586081

Validations and rules tuning

Resolved in Pega Version 8.3.5

Issues relating to an extra row being added to auto-populated properties, adding a 'when' visibility to a picklist property, and errors saving nested properties have been resolved, and performance of the overall system has been improved.

INC-144601 · Issue 602424

Empty addresses removed from email

Resolved in Pega Version 8.3.5

After upgrade, an issue was seen when sending email to multiple 'To' addresses generated an exception if any 'To' address had an empty value. To resolve this, a check has been added that will remove any empty address from the recipientTo address list.

INC-143622 · Issue 602980

Improved privacy for email listener alerts

Resolved in Pega Version 8.3.5

To improve privacy, the customer 'from' address will be removed from PEGA0011 alerts for email listener processing.

INC-130176 · Issue 585374

Removing PageList removes all cached pages

Resolved in Pega Version 8.3.5

A previous change was made such that when removing a pageList property, its size is removed from the size-specific cache as well. A further enhancement has been made so that when a PageList is removed, the system will clear the pageCache of all cached pages in the PageList.

INC-133583 · Issue 584923

Rest connector supports extended chars in attachments

Resolved in Pega Version 8.3.5

When the pyRequestAttachmentPage clipboard page was populated with a file name that contained Latin supplemental 1 unicode characters (decimal values 160 to 255 - for example an umlaut), any extended characters were being converted to question marks (?) before the call was sent, causing the web service call initiated by Pega to fail. To better support this use, an enhancement has been added to support a multipart request with extended characters in the file name. This allows the pyRequestAttachmentPage to specify pyFileNameExtendedChars, allowing RFC 6532 mode to be toggled for multipart requests with attachments. This mode allows for UTF-8 encoding in the attachment file name header, rather than the default ASCII encoding.

INC-143461 · Issue 601841

Updated JSON DT nested page property handling

Resolved in Pega Version 8.3.5

In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a pagelist property is given, the pagelist was populated with only one result but the single-page property was treated like a pagelist and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested PageLists.

INC-139297 · Issue 601421

JSON content type update

Resolved in Pega Version 8.3.5

An update has been made to ensure the content_type is set to application/json for JSON response.

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