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-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.

INC-134932 · Issue 578544

Timeout for node to join cluster increased and made configurable

Resolved in Pega Version 8.5.1

Hazelcast timeouts were causing application restart failures. This was traced to a rare case scenario of heavy processing on the primary node causing the new node to not be able to join the cluster within the designated 5 minute threshold. To compensate for this, the default time to join has been increased to 9 minutes and a prconfig setting has been added to configure the time setting.

INC-133270 · Issue 581839

Automatic agent restart added for temporary connection issues

Resolved in Pega Version 8.5.1

An agent that was stopped due to an issue with the database connection did not recover when the connection was reestablished. To resolve this, updates have been made that will handle an automatic restart of the agents when there are temporary connection issues.

INC-135359 · Issue 587038

CORS header configuration added for Stream tier

Resolved in Pega Version 8.5.1

An enhancement has been added that allows setting the CORS header (Access-Control-Allow-Origin) to allow *.DOMAIN.com on Stream tier (/stream/view & /stream/click) calls by way of the setting /stream/httpHeaders .

INC-134069 · Issue 583024

Added Kafka logging

Resolved in Pega Version 8.5.1

In order to help diagnose issues encountered during Kafka background processing, additional logging has been added to QueueProcessorDatasetHandler.

INC-142792 · Issue 594499

Modified thread data page cleanup

Resolved in Pega Version 8.5.1

Some cases were becoming stuck at a particular stage and not proceeding further even though the task in the backend was complete. Investigation traced this to work done that removed declarative pages at the thread level to optimize performance while other clipboard pages were retained, and the issue has been resolved by deleting all thread data pages after every item processed by the agent.

INC-125122 · Issue 581255

JMX authentication added

Resolved in Pega Version 8.5.1

Support has been added for JMX authentication through user and password.

INC-130886 · Issue 590374

Bad Stream error after passivation resolved

Resolved in Pega Version 8.5.1

A "Bad Stream" error was seen when attempting to reassign a case to the Workbasket, and a save of the work object failed. This was caused by a corruption of the work object during passivation, and has been resolved.

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