SR-B31667 · Issue 289067
Consistent Work IDs between case types created in different implementations
Resolved in Pega Version 7.3
Creating an Implementation layer on the Warranty application using the New Application wizard of Pega 7.22 GA was resulting in a different Work ID prefix of some case types like Claim Unit or Appeal than when the same case types were created in the built on application. This was traced to different activities being used to populate the data page, and has been updated to ensure uniform work ID generation.
SR-B31748 · Issue 291859
Stage SLA urgency correctly updates
Resolved in Pega Version 7.3
Stage SLA was updating the wrong urgency property due to the urgency value being added twice. The ExecuteSLA activity has been modified to make sure that urgency value for stage and step are updated correctly.
SR-B31778 · Issue 294184
First column name displays in tree grid
Resolved in Pega Version 7.3
The first column name was not appearing in the tree grid using the freeze header configuration. This has been fixed.
SR-B31778 · Issue 290725
First column name displays in tree grid
Resolved in Pega Version 7.3
The first column name was not appearing in the tree grid using the freeze header configuration. This has been fixed.
SR-B31778 · Issue 301431
Fixed tree grid column alignments for Internet Explorer/ Chrome
Resolved in Pega Version 7.3
When using freeze headers with fill 100% width, Internet Explorer and Chrome showed alignment issues between the header and content columns in a tree grid. This was caused by a missing semicolon in the inline style of left grid header for tree grid, which has been fixed.
SR-B31818 · Issue 292373
Security update for URL string queries
Resolved in Pega Version 7.3
To ensure sensitive information is not exposed in transit between the client and server via URL query string parameters, pyCaseManager Menu and pzGetUserProfile activity have been updated to avoid passing the user ID as a parameter.
SR-B31818 · Issue 292752
Security update for URL string queries
Resolved in Pega Version 7.3
To ensure sensitive information is not exposed in transit between the client and server via URL query string parameters, pyCaseManager Menu and pzGetUserProfile activity have been updated to avoid passing the user ID as a parameter.
SR-B31825 · Issue 288489
Documentation correction for service-enabled system management
Resolved in Pega Version 7.3
The help file for service-enabled system management has been updated to correct and clarify the full path used for connection properties in conjunction with the --connPropFile argument.
SR-B31873 · Issue 298086
Review/Perform harness modifications for scheduled report errors
Resolved in Pega Version 7.3
Scheduled reports would periodically go to Completed state and stop running prematurely. Deleting and then reopening a scheduled report (from recents) caused corruption of scheduled reports that are re-scheduled. This was traced to the Review/Perform harness going in to a corrupt state, and has been corrected by re-building the Review harness as well as some minor changes to the Perform harness to ensure the correct buttons are displayed when deleting a scheduled report and reopening it from the recents list.
SR-B31876 · Issue 290136
Correspondence logic corrected for party ID
Resolved in Pega Version 7.3
When using the Send Email smart shape to send correspondence to work party, party Roles containing the string "Owner" (such as "AAOwner") caused the correspondence to be sent to the email address of the "Owner" party instead of the "AAOwner" party. This was caused by a logic error in the party list iteration that used 'contains' instead of 'equals', and has been fixed.