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 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.

INC-178148 · Issue 660924

Handling added for SSO servlet name

Resolved in Pega Version 8.7

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 673063

Handling added for SSO servlet name

Resolved in Pega Version 8.7

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 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-D38492 · Issue 505489

Batching now enabled when using IH Summary shape in substrategies

Resolved in Pega Version 8.2.4

Batching was not being enabled when using IH Summary shape in substrategies. This was traced to the IH_SUMMARY_CACHE field not automatically being passed to sub-strategies, and has been corrected.

SR-D39003 · Issue 505997

Threads will be updated to maintain assembly context when using Static Assembler

Resolved in Pega Version 8.2.4

When running the Static Assembler utility from UI, the assembler process completed successfully but the PegaRULES.log was flooded with the FATAL exception "Usage error - next Executable not based on current". This error was generated from com.pega.pegarules.session.internal.mgmt.Executable constructor, and indicated an issue with the thread context being different from the assembly context. To resolve this, the system has been modified to update the context of thread to what is expected as assembly context.

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.

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.

INC-175630 · Issue 653863

Application selections only announced when visible

Resolved in Pega Version 8.7

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-D26785 · Issue 495892

Corrected error when persisting temporary work object

Resolved in Pega Version 8.2.4

When persisting a temporary work object using the Persist case shape, the internal assignment handle was not updated to include the work object's ID. Subsequent attempts to access the internal assignment (such as the "Edit" button on the Review Harness) resulted in errors. Investigation showed that when a temporary case was persisted, pyInternalAssignmentHandle was not getting recalculated after pzInsKey was updated. To resolve this, the configuration on the edit button has been modified to use .pxFlow(pzInternalCaseFlow).pxAssignmentKey which is what pyInternalAssignmentHandle declare expression was also returning.

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