Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

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 SR ID number in order to find the associated Support Request.

INC-133026 · Issue 578278

Updated Pulse email attachment handling

Resolved in Pega Version 8.4.3

After updating from 8.3.2 to 8.3.3, the Audit Trail displayed the entire contents of an email. In some instances, attaching a .txt file caused the file extension to be displayed twice. This was due to pyNote being used to create email file posts, and has been resolved by updating the implementation to use pyEmail instead of pyNote. Backward compatibility has been ensured by still considering pyNote for older emails and changing when emails open.

INC-136264 · Issue 582470

Chatbot text starts scroll at top of answer

Resolved in Pega Version 8.4.3

In order to present an improved interface for customers interfacing with chatbots, the code has been updated so that the recipient's chat scroll will remain at the top of an answer that would scroll off the screen.

INC-139018 · Issue 587714

Rules updated to handle Outlook change that displayed multiple/duplicate email responses

Resolved in Pega Version 8.4.3

In Pega Email Triage case, all the replies were displayed along with the original email body, meaning for each and every reply, Pega showed the original email body and duplicated the data. This was traced to an update made by Microsoft in the Selector function of Outlook Windows, and has been resolved by updating the rules 'PyExtractLatestReplyFromHTML' and 'pyRichTextEmailHistorySelector' to work with this change.

INC-137709 · Issue 584295

New security role added to restrict access to development-specific classes

Resolved in Pega Version 8.4.3

A new security role and related RAROs have been implemented to allow better security for end users on non-BAC systems. This restricts access to Rules and execution of activities on classes that are development-specific.

INC-139300 · Issue 590270

Additional security for encrypted passwords

Resolved in Pega Version 8.4.3

Handling and cleanup has been updated for encrypted values to enhance security.

INC-130145 · Issue 582854

Null checks added for the presence of roles and dependent roles

Resolved in Pega Version 8.4.3

Frequent Null Pointer errors were being generated relating to SecurityAnalysisForSecurityAdministratorsTask.getCurrentSecurityTaskDetails(). Investigation showed that the Origin and Stack trace tabs were empty, leading to the obj-open of the role failing when the role was not available in the system being utilized. This has been resolved by adding a series of null checks for role existence and dependent roles existence.

INC-130500 · Issue 580622

Cross-site scripting protections updated for authorization

Resolved in Pega Version 8.4.3

Cross-site scripting protections have been updated for various URLs associated with authorization.

INC-134315 · Issue 578368

Resolved 400 error on second browser session

Resolved in Pega Version 8.4.3

When accessing application URLs in two tabs of a browser window, logging into the second session was throwing a 400 invalid request. This has been resolved by adding specified activities to an allow list which will bypass URLObfuscation in un-authenticated mode. Non-listed activities will be processed using URLObfuscation if it is enabled.

INC-135849 · Issue 582938

Encrypted SOAP response token generation updated

Resolved in Pega Version 8.4.3

After configuring a SOAP service that used signature and encryption on the response, the response being created was incorrect and could not be decrypted by the receiver. Investigation showed that the API used to generate the SOAP headers was not setting the wsse11:TokenType element, causing receivers which enforce BSP compliance to fail. This has been resolved by modifying the custom webservices-rt-pega2 jar to set the token type in the case of a response encryption policy.

INC-138354 · Issue 584720

Handling added for samesite cookies with httpOnly

Resolved in Pega Version 8.4.3

After enabling samesite cookies on Google Chrome to support Mashup login, intermittent issues were seen with a non-mashup login where entering the OperatorID and password only resulted in a refresh of the login screen. This was traced to a scenario where an httponly cookie attribute was present along with samesite cookie attributes, and has been resolved by adding handling for a condition where samesite is set and httpOnly is enabled.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us