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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-B90299 · Issue 339920

Logic added to handle empty operator value in FCM stepup

Resolved in Pega Version 7.4

As part of FCM step up, trying to 'Retrieve information' from the stub case in the master instance did not return any result. This was traced to the operator parameter value not being mapped and therefore passed as blank to the service activity pxDiscoverCaseTypes, which resulted in the activity being skipped. Logic has now been added to handle cases where the mapped value is not available.

SR-C10816 · Issue 352778

Help updated for Tracing Service rules

Resolved in Pega Version 7.4

The help files for tracing services have been updated to reflect that Service Rules cannot be traced in production environment (where the prod level is set to 5) unless the following DSS is set to be 5: Pega-RulesEngine trace/cluster/ServiceRuleWatchMaxProductionLevel

SR-C3565 · Issue 348201

Connector simulations for dotNet evaluated correctly

Resolved in Pega Version 7.4

After upgrade, simulation activity added to a dotNet connector rule resulted in the pyConnectorType being saved as SOAP instead of as dotNet. This was due to the code validating pyConnectorType property value with the Connector class endsWith, and has been fixed.

SR-C4285 · Issue 348400

Added handling for Connect-REST response containing "null"

Resolved in Pega Version 7.4

Connect-REST was generating a NullPointerException when the response value contained 'null'. This has been fixed.

SR-C6601 · Issue 348759

Added handling for Connect-REST response containing "null"

Resolved in Pega Version 7.4

Connect-REST was generating a NullPointerException when the response value contained 'null'. This has been fixed.

SR- · Issue 319981

Field labels localized in pyAccountSettings

Resolved in Pega Version 7.4

Localization has been added to the field labels in the pyAccountSettings section rule.

SR- · Issue 324033

Files updated to resolve memory leaks

Resolved in Pega Version 7.4

The following files have been updated to address memory leak issues when processing a large number of cases: PZPEGA_UI_DYNAMICCONTAINER_LITE PZPEGA_PROCESS_ENGINE PEGA_TOOLS_EVALDOMSCRIPTS PZPEGA_UI_DOC_LIFECYCLE PZPEGA_CONTROL_DROPDOWN

SR-B47513 · Issue 328997

Logic updated for expandAll to resolve CME

Resolved in Pega Version 7.4

A concurrent modification exception was appearing on a node level page when using expandAllToproperties due to two threads simultaneously trying to expand the page. This has been fixed by modifying the logic in expandAll(true, true).

SR-B64115 · Issue 330040

Handling and logging added for null PRThread tenant ID

Resolved in Pega Version 7.4

In cases where no PRThread was not found from the thread container when writing a ruleset index to DB, the tenant ID was lost and the system used the default "Shared". This resulted in a tenant RSL shown twice in the DB, one as the tenant itself and the other as Shared. Two changes have been made to resolve this: first, debug logging has been added to the stack trace if the thread is null, and second, if this happens in a MT environment, the system will skip writing to the DB so the tenant TSL will not be given as Shared.

SR-B64115 · Issue 329896

Handling and logging added for null PRThread tenant ID

Resolved in Pega Version 7.4

In cases where no PRThread was not found from the thread container when writing a ruleset index to DB, the tenant ID was lost and the system used the default "Shared". This resulted in a tenant RSL shown twice in the DB, one as the tenant itself and the other as Shared. Two changes have been made to resolve this: first, debug logging has been added to the stack trace if the thread is null, and second, if this happens in a MT environment, the system will skip writing to the DB so the tenant TSL will not be given as Shared.

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