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-160485 · Issue 655296

Trailing "/" added to public links for SSO use

Resolved in Pega Version 8.5.5

Links generated using pyWorkLinkWithLabel were not working with SSO due to not having a trailing "/" on the URL. This has been corrected by adding code to append the "/" if the public link url doesn't end with it.

INC-178148 · Issue 660926

Handling added for SSO servlet name

Resolved in Pega Version 8.5.5

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.

SR-A2424 · Issue 205812

Latency resolved for sites with repeated SAML authentication requests

Resolved in Pega Version 7.1.9

In an installation using SAML SSO for authentication, repeatedly initiating SAML IDP requests were eventually causing poor system performance. To resolve this, support has been added to disable replay cache handling during SSO login via a DSS.

INC-174267 · Issue 657129

Wait action persists when using Urgency Adjustment

Resolved in Pega Version 8.5.5

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-A3897 · Issue 209254

Resolved authentication requirements in activity pzSetQueryDefaults for SSO setup

Resolved in Pega Version 7.1.9

Code-Security.InitialProfileSetup does not need authentication to run, but during the SSO login it calls Code-Pega-Requestor.pzSetQueryDefaults which was hard-coded to require authentication. This was an error, and the SetQueryDefaults activity no longer requires authentication.

SR-A692 · Issue 205611

Resolved duplicate portal open when using Microsoft Internet Explorer 11

Resolved in Pega Version 7.1.9

When using Microsoft Internet Explorer 11, trying to access the My Group tab in the links 'Manage Operator Schedules and Profiles' was not displaying the screen correctly on click of any operator or workbasket and an extra portal window was opened. This was a browser-specific dynamic container issue where the lack of an explicit type=button declaration was causing a form submit that triggered a main page refresh. That declaration has been added.

INC-176112 · Issue 656971

When rule inside a loop correctly picked

Resolved in Pega Version 8.5.5

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-A2009 · Issue 206469

Fixed inconsistent tab 'visible when' behavior

Resolved in Pega Version 7.1.9

In a section with a tabbed repeat using 'body visible when', invoking a list which changed the when condition so that the tab becomes visible in the tabbed repeat created various issues after checking the visibility including invisible data, empty tabs, and duplicate tabs. This was traced to the placement of visible when conditions in the RUF causing the DIVs to be closed incorrectly, and has been fixed.

INC-175630 · Issue 653862

Application selections only announced when visible

Resolved in Pega Version 8.5.5

The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.

SR-A168 · Issue 203378

Enhancements added to ensure visible 'when' after upgrade

Resolved in Pega Version 7.1.9

After migration using systems upgraded in place, all pre-existing Default controls no longer showed the "Required" option in the cell properties, and the validation no longer functioned correctly (the form submitted successfully with previously required fields empty). The root cause was that pyAutoHTML was not set in XML, so the Visibility condition expression evaluated to false. This has been resolved by adding a check for empty visible-when conditions and by inserting pzNonAutoHTML, a newly created when rule which checks for empty or false values of pyAutoHTML for required checkbox visibility.

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