SR-C3921 · Issue 349058
Handling added for idled WO with empty values
Resolved in Pega Version 7.4
After opening a work object and then idling it for at least 15 minutes, trying to perform a Word merge resulted in HTML code being inserted into previously empty values. This has been corrected.
SR-C6529 · Issue 350614
Edit Pipeline trigger on merge state resolved
Resolved in Pega Version 7.4
The property "pyStartBuildOnBranchMerge" (which corresponds to the UI setting called "Trigger build on merge" on the 'Add Application pipeline') was not changed as expected when using the Actions>Edit Pipeline to alter the state of "Trigger build on merge". This was true whether the option was being switched OFF or ON, with the setting remaining fixed at its original state. This was traced to pyStartBuildOnBranchMerge persisting after being deleted, and has been resolved by defaulting the value of pyStartBuildOnBranchMerge to false to allow the calculation of the pyStartBuildOnBranchMerge state to work correctly.
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.
SR-B67903 · Issue 331567
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.
SR-B70116 · Issue 328876
Missing backlink fixed for deferred save
Resolved in Pega Version 7.4
Reference errors were generated when opening a work object on an end user portal due to the backlink on an empty source property being lost during a deferred save operation. This has been fixed.