SR-B14774 · Issue 285008
Optional Process Child Case correctly sets ObjectClass
Resolved in Pega Version 7.3
When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.
SR-B14774 · Issue 285027
Optional Process Child Case correctly sets ObjectClass
Resolved in Pega Version 7.3
When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.
SR-B1478 · Issue 274489
Better handling for empty LockInfo page
Resolved in Pega Version 7.3
Intermittent errors were encountered when attempting to expand rows of a repeat grid. This was due to handling difference related to a pre-condition check for the LockInfo page used to create error messages. Since the LockInfo page is not required or consistently used, the system has been updated to better handle cases where it is empty.
SR-B14866 · Issue 285387
ClipboardPageAdapter retains pxObjClass values in page-lists
Resolved in Pega Version 7.3
When adapting clipboard pages from Pega Platform pages to DSM pages, the ClipboardAdapter was reverting page-list items to the obj-class defined on the property instead of keeping the actual class. This was traced to an issue with the conversion method between DSM pages and regular ClipboardPages, and has been fixed.
SR-B14866 · Issue 275830
ClipboardPageAdapter retains pxObjClass values in page-lists
Resolved in Pega Version 7.3
When adapting clipboard pages from Pega Platform pages to DSM pages, the ClipboardAdapter was reverting page-list items to the obj-class defined on the property instead of keeping the actual class. This was traced to an issue with the conversion method between DSM pages and regular ClipboardPages, and has been fixed.
SR-B14905 · Issue 284489
Handling added for unexpected BLOB forms during multi-tenant initialization
Resolved in Pega Version 7.3
The PegaRULES engine was failing to initialize if it encountered a BLOB that was corrupt, null, empty, abruptly small sized, or less than 4 characters long when iterating through Data-Admin-Tenant records. An explicit check has been inserted to resolve this, which will throw a bad record exception with more information before trying decrypt.
SR-B1495 · Issue 273198
Workaround to resolve HP NonStopDB column label bug
Resolved in Pega Version 7.3
Using HP Non Stop DB as an external DB with Type 4 driver caused Connect-SQL with Browse to generate the error "UNKNOWN_COLUMN_0: Column number 0 has an invalid name errors in clipboard" but still return the data. This was traced to a bug in the HP driver that caused the getColumnLabel() to be returned as empty, and the system has been updated to return the Column Name when Column Label is null or empty to overcome this.
SR-B15101 · Issue 296224
Logic added to convert UTC Date for REST clipboard mapping
Resolved in Pega Version 7.3
An error was generated while mapping UTC format Date fields to the clipboard in REST. This was traced to the DateTime properties in the JSON response not being converted to Pega-supported datetime format, and the necessary parsing logic has been added.
SR-B15138 · Issue 285032
RUF and listener updates made to support new version of Bouncy Castle
Resolved in Pega Version 7.3
Compatibility issues were found with Bouncy Castle 1.49 and newer versions of WebLogic. In order to proceed with updating Bouncy Castle to the latest version, the SendEmailMessage RUF in Pega-IntegrationEngine and Pega-Procom has been modified to adhere to the newer Bouncy Castle APIs, and the email listener has been updated. The logic related to Rule utility function compilation has been changed to only to consider the top version of a library.
SR-B15143 · Issue 285148
Garbage Collector access fixed in Logging screen
Resolved in Pega Version 7.3
SMA Garbage Collector information was not available under Logging and Tracing due to a naming error; this has been fixed.