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-178148 · Issue 660925

Handling added for SSO servlet name

Resolved in Pega Version 8.6.2

After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.

INC-188405 · Issue 673065

Handling added for SSO servlet name

Resolved in Pega Version 8.6.2

After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.

INC-174267 · Issue 669672

Wait action persists when using Urgency Adjustment

Resolved in Pega Version 8.6.2

When using the Urgency Adjustment (pyAdjustAssignmentsla standard local action), once a case reached the wait action and the goal and deadline were updated the previous pyWaitAction was not being stored. This has been resolved by ensuring the previous pyWaitAction will be stored and passed to the AddAssign activity.

SR-D64566 · Issue 547513

Option added for redirect to SAML IDP on logout

Resolved in Pega Version 8.3.3

An enhancement has been added which provides a check box to choose to redirect to SAML IDP on logout from Pega.

SR-D80539 · Issue 544793

Testcases are not available for 'access when' rules

Resolved in Pega Version 8.3.3

Attempting to create test cases for access when rules resulted in guardrail warnings about the need to create a test case. Because Test Cases are not available for the Access When rule type as per Pega expected behavior, the guardrail warnings are not valid and have been removed.

SR-D88451 · Issue 550847

Testcases are not available for 'access when' rules

Resolved in Pega Version 8.3.3

Attempting to create test cases for access when rules resulted in guardrail warnings about the need to create a test case. Because Test Cases are not available for the Access When rule type as per Pega expected behavior, the guardrail warnings are not valid and have been removed.

INC-176112 · Issue 662449

When rule inside a loop correctly picked

Resolved in Pega Version 8.6.2

While using a 'when' rule inside a loop of a page list, the rule was not being picked during runtime. This has been resolved by adding an update to allow an assembly time class name to be passed into runtime.

SR-D53176 · Issue 541792

Error when adding function filter will persist

Resolved in Pega Version 8.3.3

When an exception occurred while adding a filter in the report viewer, the error was shown but cleared due to an immediate refresh of the parent section. Analysis found that step2 of pzGetFiltersFromContent was failing, after which the error was shown, the section reload happened, and the error disappeared. To resolve the error being cleared prematurely, the pzOnLoadReloadReport control has been modified so that when there are messages on the top level page (pyReportContentPage), a parameter will be set on HarnessContextMgr to not to clear them during the next refresh call.

SR-D85653 · Issue 548599

Repaired Tracer use with Google Chrome

Resolved in Pega Version 8.3.3

After running Tracer while using Google Chrome, closing it and trying to run another resulted in an error indicating "Cannot Launch multiple tracer sessions for a requestor". This was identified as a bug with Google Google Chrome Versions greater than 70 and was caused by Google Chrome deprecating the use of sync XHR on page dismissal, and has been resolved by modifying the system to use a beacon API instead.

SR-D90051 · Issue 549492

Repaired Tracer use with Google Chrome

Resolved in Pega Version 8.3.3

After running Tracer while using Google Chrome, closing it and trying to run another resulted in an error indicating "Cannot Launch multiple tracer sessions for a requestor". This was identified as a bug with Google Google Chrome Versions greater than 70 and was caused by Google Chrome deprecating the use of sync XHR on page dismissal, and has been resolved by modifying the system to use a beacon API instead.8.4.1: 546596

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