SR-B14688 · Issue 289060
Parameter added to consider production rulesets while checking rule resolution
Resolved in Pega Version 7.3
After creating a portal for admin users and adding it to a production ruleset that in turn had been added to the appropriate application and access group, adding the portal to the access group unexpectedly generated the error "Portal name: is not a Valid Record for use by this Rule." This was due to the system not considering production rulesets while checking rule resolution, and the parameter pyUserPreproductionrulesets has been added to the validate activity to handle this.
SR-B14732 · Issue 296513
Resolved error with DateTime property comparison crossing daylight savings time
Resolved in Pega Version 7.3
If an operator was using time zone "Europe/London" and locale "en_US", an error occurred when comparing two dates if the property type was DateTime and one of the dates selected in Date range fell under daylight savings time. The error did not occur if the property was of type Date. The addCalendar RUF has been updated to resolve this issue.
SR-B14732 · Issue 296847
Resolved error with DateTime property comparison crossing daylight savings time
Resolved in Pega Version 7.3
If an operator was using time zone "Europe/London" and locale "en_US", an error occurred when comparing two dates if the property type was DateTime and one of the dates selected in Date range fell under daylight savings time. The error did not occur if the property was of type Date. The addCalendar RUF has been updated to resolve this issue.
SR-B14745 · Issue 285506
pzSUS Param properly URLEncoded
Resolved in Pega Version 7.3
The Tomcat 8+ server was rejecting DWA URLs due to characters such as {,} that it considered to be unsafe. These characters were introduced by pzSus key in the URL, and these values will now be encoded for the browser to resolve these issues.
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.