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.

SR-C84361 · Issue 437601

Added handling for better recovery and reset when using 'When' conditional row deletion

Resolved in Pega Version 8.1.5

Given a 'When' condition configured so that a specific row could be deleted, trying to delete another row resulted in the expected error indicating it was not possible to delete that particular row. However, attempting to then delete the row with the 'When' condition caused the same failure error to appear which could not be cleared through clicking on the Refresh button for the section. In order to resolve this, handling has been added for a scenario where Obj-Delete fails and the record is marked for deferred commit. In this situation, the system will revert Obj-Delete by way of Obj-Save-Cancel in @baseclass.pzDeleteRecord so that a subsequent Obj-Delete does not pick up the previous record and fail again.

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.

INC-130299 · Issue 583924

Updated SSO operator authentication handling after passivation

Resolved in Pega Version 8.1.9

With SSO enabled and the pyAccessGroupsAdditional value list populated with the Mapping tab, attempting to access an expired session with an old cookie resulted in a stale thread exception while mapping value list attributes. This was due to using an AuthServicePage which was created by another session thread that had become stale for current session, and has been resolved by updating the code to call the authenticateoperator method on the authservicepage copy.

SR-C93726 · Issue 435287

Work status icons work correctly when using localization

Resolved in Pega Version 8.1.5

The pyWorkAssignmentStatus control was not displaying the status flags/icons for localized work status values due to a match failure caused by the system using the localized text for the pyAssignmentStatus to perform a string comparison against the hard-coded English values. To correct this, the control pyWorkAssignmentStatus has been modified to run the comparisons with the new string "assignmentStatus" instead of with the localized text.

SR-C97873 · Issue 437282

Added check to maintain key value when using collapseAllMenu in child navigation menu

Resolved in Pega Version 8.1.5

After a navigation menu had a child added as reference navigation menu that used the function collapseAllMenus, the screen was freezing if a link was clicked in the added child navigation and a javascript error appeared on the console screen. This was traced to an improper key being set in sessionStorage object in setItem due to the nesting, and has been corrected by adding a check in sessionstorage setitem to maintain the proper key value.

SR-C91220 · Issue 430364

Modified pzpega_ui_dynamiccontainer to resolve issue with editing the Operator rule form when using IE

Resolved in Pega Version 8.1.5

The Operator rule form was not opening a second time after being updated in IE. The form worked as expected with other browsers. This has been resolved by modifying the openRuleByKeys function in pzpega_ui_dynamiccontainer to pass a new cloned object to the JSON.stringify function instead of the embedded object.

INC-130677 · Issue 570040

When rule accepted in column header

Resolved in Pega Version 8.1.9

A grid was not rendering if it contained a 'when' rule on a column header. This was a missed use case and has been resolved.

INC-146837 · Issue 602673

PerformCriteria contains CurUserHasRequiredSkills 'when' rule

Resolved in Pega Version 8.1.9

A customer version of the PerformCriteria data transform was generating a validation error due to a qualified statement that resulted in a null result. This has been resolved by updating the PerformCriteria DT to include the CurUserHasRequiredSkills 'when' rule.

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