SR-C57 · Issue 344928
Check added for Manage Participant work parties
Resolved in Pega Version 7.4
Expected work parties were not displayed in Manage Participant due to a missed use case. A check for the prefix "|" has been added before removing the repeatable work party in step 4 of pyGetWorkPartyOptions & getWorkPartyOptions activities.
SR-C9329 · Issue 350197
Duplicate cases issue fixed
Resolved in Pega Version 7.4
Duplicate cases were shown in worker case compensation due to a case-sensitive values check. The 'when' condition has been modified to correct this.
SR-C9808 · Issue 351050
Resolved duplicate assignments in app
Resolved in Pega Version 7.4
Assignments were being duplicated in the app due to the system using a stale cover page. This has been corrected.
SR-B82808 · Issue 331981
Correspondence Message in the audit history no longer truncated
Resolved in Pega Version 7.4
Because SendSimpleEmail sets pyLabel to the first 64 characters of pySubject and pyLabel is limited to 64 characters, messages in the audit history were often truncated. In order to allow the full correspondence subject to be included in the audit history message, pySubject has been modified to use Param.MemoForEmail in SendSimpleEmail and pass it to CorrAttach activity to add the complete subject in the history.
SR-B87297 · Issue 339969
Decision tree error fixed
Resolved in Pega Version 7.4
When trying to open a "SetCorrSalutation" Decision tree object, a blank page appeared and the system became unresponsive. Investigation showed this was due to stack overflow errors related to the regex pattern used in the activity 'Embed-Rule-Declare-DecisionTree! pzFBPostActivity', and the rule Embed-Rule-Declare-DecisionTree ! pzFBPostActivity has been modified to optimize the regex.
SR-B90177 · Issue 337875
Removed extra spaces in attached note
Resolved in Pega Version 7.4
After attaching a note, extra line spaces were seen in the note. This has been fixed.
SR-B91572 · Issue 339656
Email addresses passed intact
Resolved in Pega Version 7.4
When sending correspondence with a Bcc recipient, the Bcc recipient Email ID had the last letter removed in "populateRecipients". This has been fixed, and additional checks have been added for the other address fields as well.
SR-B91999 · Issue 340444
Smart email reply error fixed
Resolved in Pega Version 7.4
An exception was generated when attempting to reply in SmartEmail. This was traced to different APIs conflicting and overriding the address setting process, and the system has been modified to correct this.
SR-B91999 · Issue 336429
Smart email reply error fixed
Resolved in Pega Version 7.4
An exception was generated when attempting to reply in SmartEmail. This was traced to different APIs conflicting and overriding the address setting process, and the system has been modified to correct this.
SR-C2673 · Issue 344715
Email addresses passed intact
Resolved in Pega Version 7.4
When sending correspondence with a Bcc recipient, the Bcc recipient Email ID had the last letter removed in "populateRecipients". This has been fixed, and additional checks have been added for the other address fields as well.