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-177737 · Issue 663141

Authentication requirement updated for CallConnector

Resolved in Pega Version 8.7

After update, invoking a REST API call during SSO login which eventually called pxCallConnector (Final Activity) in @baseclass Pega-RulesEngine failed at the CallConnector step. This was caused by a change in recent Pega versions which enabled authentication for this activity, and has been resolved by marking the activity as internal and disabling the authentication requirement.

SR-A24408 · Issue 248682

Page clearing added for AuthReqContex

Resolved in Pega Version 7.2.2

The page "AuthReqContex" was loaded up during SAML authentication and then passivated, but the pages were retained in the clipboard and improperly activated by an unknown thread, causing an error. This has been resolved by adding Page-Remove steps wherever needed in auth activity and logout activity (AuthReqContext, LoginInfo, ReqInfo, RelayStateInfo, and SessionInfo) to remove the pages that are no longer needed.

SR-A94633 · Issue 261954

Mouse clicks work on touchscreen/mouse combo devices

Resolved in Pega Version 7.2.2

When using Google Chrome with a touchscreen and mouse combination, some click events such as Calendar date picker were not working when using the mouse. This was due to MenuSystem not using the generic isTouchable API, and this has been updated.

SR-117844 · Issue 170991

Auto-refresh only available for Section Tabs

Resolved in Pega Version 7.1.7

When the "Refresh when active" checkbox was checked in a harness used in the Case Manager dashboard, creating or closing a WO did not update this page automatically. This is because auto-refresh is unsupported in the harness; it is better to use Section Tabs (the best practice statement explains why) and they are encouraged over using Harness tabs. In order to make this use clear, the auto-refresh checkbox will not be displayed in harness tabs.

INC-187553 · Issue 675429

Service Email handling updated for MSGraph "From" address

Resolved in Pega Version 8.7

While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.

INC-188080 · Issue 673783

Service Email handling updated for MSGraph "From" address

Resolved in Pega Version 8.7

While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.

INC-188143 · Issue 674972

Service Email handling updated for MSGraph "From" address

Resolved in Pega Version 8.7

While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.

INC-189477 · Issue 674034

Service Email handling updated for MSGraph "From" address

Resolved in Pega Version 8.7

While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.

INC-200029 · Issue 690167

Service Email handling updated for MSGraph "From" address

Resolved in Pega Version 8.7

While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.

INC-154205 · Issue 618737

Corrected wrap text for Cosmos radio buttons

Resolved in Pega Version 8.6

When using Cosmos, radio buttons with large labels were displayed with the text overlapping even when wrap text was enabled and the radio button placement was incorrect. This was traced to a height of 32px being set as the default, overriding the wrap text setting, and has been resolved by adding CSS to set the height as auto when wrap text on radio label is used.

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