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.

SR-D29127 · Issue 506863

SAML data pages restored after passivation

Resolved in Pega Version 8.2.4

If login used SAML SSO, resuming the session after passivation resulted in missing or empty data pages when using an SAP integration with Pega Cloud. This was traced to a security change that modified the D_SAMLAssertionDataPage and D_SamlSsoLoginInfo data pages as readonly, causing them to not be passivated under these conditions. To resolve this, the data pages have been made editable so they will be restored as expected. This change also resolves any difficulty with SAML logoff activities in conjunction with SAP and Pega Cloud.

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.

SR-C67397 · Issue 421638

Added check for missing rule data when using abstract class in CSS

Resolved in Pega Version 8.2.1

Including CSS optimization with abstract class in the Advanced tab of the 'Add Optimization' Screen resulted in a Null pointer exception error. This has been resolved by adding a check for missing data from a rule to make the system more resilient in its handling of a corrupt flow-action clipboard page.

SR-C80372 · Issue 425075

Oniine help files updated to more completely reflect SAML Authentication Rule Form fields

Resolved in Pega Version 8.2.1

The online help files have been updated to reflect that the SAML Authentication Rule form has various fields including Entity Identification, Login Location, Logout protocol binding, and Artifact Resolution Service Location that support GRS syntax (=D_myDataPage). When configuring SAML it is also required to update WebSSO Service Package to point to the Access Group as the Application Access Group. https://community.pega.com/sites/default/files/help_v74/procomhelpmain.htm#concepts/concepts2/globalresourcesettingfields.htm

SR-D39302 · Issue 507981

Report name in tab uses localization

Resolved in Pega Version 8.2.4

After creating a field value with field name as pyCaption to localize the report definition name, the title in the report definition tab was not translated. This was traced to Step 1 of the activity displayReport using an old localization function, and has been resolved by changing the localization of document title to use pyCaption.

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.

SR-D29809 · Issue 505256

Extra <p> tag removed when not needed in RTE generation

Resolved in Pega Version 8.2.4

The RTE was generating an extra <p> tag in the Review harness or when the RTE was non-editable, causing alignment issues in the UI when RTE was displayed using inline dynamic layout with a textarea. This has been corrected.

SR-C89656 · Issue 426423

Case urgency value will not be reset when processing wait shapes

Resolved in Pega Version 8.2.1

When a Wait shape was configured with the ‘Users can choose to continue process’ option unchecked, the overall work object SLA urgency was overwritten to 0 when the SLA processed the Wait shape. This was due to the Wait shape using pzWaitTImer, which has all urgency values as 0. The SLA being set to 0 did not occur if ‘Users can choose to continue process’ was checked on the Wait shape because pxSystemFlow was not set to true in that case. To prevent the SLA override, a check has been added that will skip setting the urgency setting if there is a wait shape.

SR-C84921 · Issue 424317

Connection Manager uses keyring for null prconfig password

Resolved in Pega Version 8.2.1

After upgrade, credentials from BIX keyring were failing when using BIX via commandline rather than prconfig. This was traced to a behavior change in the Connection Manager, and has been resolved by modifying the Connection Manager to look up the password from the keyring when given a URL configuration where the password is null in prconfig (URL connection only).

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