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.
SR-B80438 · Issue 343243
Unauthenticated requestor timeout customizable
Resolved in Pega Version 7.4
An enhancement has been added to provide a new customizable configuration switch for the unauthenticated requestors timeout value, i.e. the short lived requestor timeout value. Previously, this defaulted to one minute.
SR-B91029 · Issue 342265
hbase config enhancement
Resolved in Pega Version 7.4
In order to support a customization, the hbase configuration has been enhanced to not only accept values from the UI, but also from various levels of Pega setup including prconfig.xml, hbase-site.xml, and dynamic system settings.
SR-B91029 · Issue 342841
hbase config enhancement
Resolved in Pega Version 7.4
In order to support a customization, the hbase configuration has been enhanced to not only accept values from the UI, but also from various levels of Pega setup including prconfig.xml, hbase-site.xml, and dynamic system settings.
SR-B92192 · Issue 342143
Unauthenticated requestor timeout customizable
Resolved in Pega Version 7.4
An enhancement has been added to provide a new customizable configuration switch for the unauthenticated requestors timeout value, i.e. the short lived requestor timeout value. Previously, this defaulted to one minute.
SR-C8717 · Issue 350603
hbase config enhancement
Resolved in Pega Version 7.4
In order to support a customization, the hbase configuration has been enhanced to not only accept values from the UI, but also from various levels of Pega setup including prconfig.xml, hbase-site.xml, and dynamic system settings.
SR-B70432 · Issue 330094
AP correctly re-evaluates half-baked data page
Resolved in Pega Version 7.4
When there is a recursion between DP load and corresponding AP load, the half-baked data page is used for populating AP. However, if the autopopulate property content was empty, the complete list data from the data page was not returned even after completion of the loader activity. This was caused by the AP not re-valuating after completion due to the activity not being marked as stale/dirty. This has been fixed.
SR-B74771 · Issue 331516
Resolved Segment List Creation errors
Resolved in Pega Version 7.4
Segment list creation was generating the error "java.sql.SQLSyntaxErrorException: ORA-01795: maximum number of expressions in a list is 1000". This was due to an error in the logic used to send the property name and csv value to post processing, and has been corrected.
SR-B74912 · Issue 337579
Handling added for '{' and '}' in data flow customerID
Resolved in Pega Version 7.4
The Data flow run was unable to process data if the special character '{' or '}' appeared in the customer ID. Other special characters executed successfully without any error. This was because these special characters are interpreted differently than others, and the issue has been resolved by prefixing these special characters with escape characters wherever encountered in the subjectID string.