SR-B13450 · Issue 284622
Null check added to joins of UserWorkList columns
Resolved in Pega Version 7.3
When attempting to join a pyUserWorkList Report definition with work class properties, blank values in the pyUserWorkList columns caused a Null Pointer exception on click of the filter icon for joined class properties/columns. This has been resolved by adding a null check.
SR-B13517 · Issue 293343
Icon alignment fixed in grids with skin inheritance
Resolved in Pega Version 7.3
The Header Title and the Collapsible Icon of a grid were misaligned due to an error in skin inheritance. The pzTemplateNewSkin1 legacy standard format has been changed to correct this.
SR-B13702 · Issue 287232
SLA correctly calculated for migrated rules
Resolved in Pega Version 7.3
After upgrade, using the case designer view to look at a case type created in an earlier version displayed errors in the right panel for the goal-HH:MM:SS and deadline-HH:MM:SS fields if the assignment had the SLA rule "Default". This was an error in backwards compatibility related to whether the "pzIsAutoGenerated" property used to distinguish the SLA was auto generated or not, and has been corrected by setting the Visibility condition .pzAutoGenerated to 'true' in the lower Dynamic layout to avoid a null value in migrated rules.
SR-B13872 · Issue 290520
StartDependencies RUF logging updated from Error to Debug mode
Resolved in Pega Version 7.3
After calling a utility to create a child case through an activity on a parent sub-flow, updating the parent case status with the "UpdateStatus" activity logged an error message that the dependent had not been created successfully. This was an unintended side effect of a logging change made for diagnostic purposes, and has been fixed by changing the logs from Error mode to Debug mode in the pzStartDependencies RUF.
SR-B14210 · Issue 284725
Autocomplete updated to handle null resultcount from data page
Resolved in Pega Version 7.3
The autocomplete control was not rendering a list supplied by data page results due to the pxResultCount being null in the results of the datapage. The count size calculation in the autocomplete function has been reworked to resolve this.
SR-B14416 · Issue 289018
Fixed double actions on repeat layout
Resolved in Pega Version 7.3
In a Grid Repeat Layout, actions added on the event 'Enter' were automatically added to event 'Click' and resulted in double actions at the runtime. This was an issue with the system incorrectly setting the pyKeyCode in pzGridActionSets Activity, and has been fixed.
SR-B14432 · Issue 286451
Editability check added to asterisk symbol (mandatory field expression) display
Resolved in Pega Version 7.3
Sections using conditional read-only and editable modes displayed the mandatory expression (asterisk symbol) in both modes. To correct this unexpected behavior, the GenerateLabelCellContent RUF has been updated to check whether the control is editable and only generate the asterisk if the result is true.
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.