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.
SR-B67903 · Issue 330405
Params passed to createNewWorkWithParams and displayed
Resolved in Pega Version 7.4
An issue with createNewWorkWithParams where parameters were not displayed in the UI even if they were available in the pyWorkPage was traced to a code function-ordering error with passing parameters to createNewWorkWithParams that caused Work Page data that was set in CreateNewWork to be overridden before it was used. This has been corrected in the process engine createNewWorkAction.