SR-B41030 · Issue 298187
Branch Merge Wizard shows up to 200 ruleset versions
Resolved in Pega Version 7.3
In the rule:pzGetVersionsForMerge List View, the page size has been changed from the previous limit of 50 to the new value of 200.
SR-B41398 · Issue 303897
Improved exception handling for "reset logging to default"
Resolved in Pega Version 7.3
After enabling debug level logging to a file, clicking "Reset all loggers to default settings" did not actually do so despite presenting a confirmation message. This was traced to incorrect handling for an exception, and has been fixed.
SR-B41409 · Issue 299554
Migrated work objects properly resolve references
Resolved in Pega Version 7.3
After upgrade, Work objects created in an earlier version were not opening due to a difference in the Reference Property Link metadata used by forward links. This has been handled by ensuring the Reference Property Links are resurrected if not explicitly present.
SR-B41433 · Issue 297836
BIX documentation updated for ExtractDataWith Args
Resolved in Pega Version 7.3
The BIX User Guide has been updated to describe how one should pass arguments when using pxExtractDataWithArgs.
SR-B41782 · Issue 297390
Improved error handling for Usage Daemon
Resolved in Pega Version 7.3
The Usage daemon was exiting due to DB error and did not recover, leading to PALSnapshotImpl multiplying and causing an OOM. This was traced to missing error handling, and UsageDaemon has now been updated to handle a DB error without exiting.
SR-B42581 · Issue 299511
BIX enhancement to handle unaligned external mappings
Resolved in Pega Version 7.3
If a class with external mappings was configured and some of the properties did not match the db column name, a filter for one of those properties would not be applied to the extract query. In order to support business needs that contain the mis-match, an enhancement has been made to the BIX code to handle this non-alignment.
SR-B42964 · Issue 302338
History table updates with data table record deletion
Resolved in Pega Version 7.3
The Deletion of the record from a data table was not adding an entry into History table. This behavior has been changed with a "History-Add" step in the pzDeleteRecord activity.
SR-B43024 · Issue 301959
Fixed focus issue for editing exported DT in Excel
Resolved in Pega Version 7.3
While editing a field in a column of a decision table exported to Excel, clicking "Insert OR After" caused the focus to be shifted to the end of the Decision table. This was traced to the sticky header applied for all the rules, and has been resolved by excluding the decision table and circumstance definition from the sticky header implementation in document.ready.
SR-B44327 · Issue 302991
Migrated work objects properly resolve references
Resolved in Pega Version 7.3
After upgrade, Work objects created in an earlier version were not opening due to a difference in the Reference Property Link metadata used by forward links. This has been handled by ensuring the Reference Property Links are resurrected if not explicitly present.
SR-B44878 · Issue 301248
displayHarness context maintained if established before passing pageName
Resolved in Pega Version 7.3
The runDataTransform() was running in the context of what was considered an incorrect page when called from the pre-js function of a Question shape when opening the case from the worklist. This was caused by using pega.offline.runDataTransform and passing the pageName parameter as null in an attempt to use the primary page context, but the system defaults to using the context of pyDisplayHarness instead of pyWorkPage when the pageName parameter is null. In order to support this configuration, the PreJS function of a question shape called from the displayHarness will maintain the context as displayHarness for pega.u.d.PrimaryPageName when passed.