INC-147873 · Issue 610864
Custom header character encoding for Subject added
Resolved in Pega Version 8.4.4
Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers.
INC-159244 · Issue 627863
Bulk actions check in preserves declare expression legacy setting
Resolved in Pega Version 8.7
When a declare expression was saved in legacy mode with "Whenever used" selected in change tracking, performing a bulk check-in of the rule caused the expression to default to the new forward chaining method. This did not occur when using a direct check-in. Investigation showed this was caused by the check-in page holding a legacy value before the step execution, and has been resolved by adding a pre-save activity before the validation activity that will restore the .pyIsLegacy value from .pyExpressionTypeSelector, if set.
SR-B88388 · Issue 340601
Resolved tracer exception on REST
Resolved in Pega Version 7.4
An exception was generated when running the tracer on the out-of-the-box Pega API data REST Service stating "The page or property dataPage.pxObjClass is unmodifiable.". This was traced to the method used to change the page class, and the code has been modified to use the alternate clipboard API to resolve this issue.
INC-174020 · Issue 650891
Performance improved for Directed Web Access (DWA)
Resolved in Pega Version 8.7
Slowness when using a Directed Web Access (DWA) link has been resolved by refining the code of the PZPEGA_UI_DOC_EVENTSCONDITIONSCHAINING script to improve performance.
SR-A2960 · Issue 218751
Asynch loaded data pages correctly pulled into main thread
Resolved in Pega Version 7.2
After using Load-DataPage, using Connect-Wait to synchronize with child requestor caused the data page to be loaded again when it was referenced instead of the system bringing the asynchronously-loaded data page forward. This was caused by differing value handling during the cache key building for ADP load, and has been corrected.
SR-A6523 · Issue 214991
Handling added for storing email addresses with special characters
Resolved in Pega Version 7.2
When attempting to store an encoded email address with special characters to the database, an exception was thrown and the process failed. This was found to be a database/data management issue related to executeRDB expression parsing the SQL query first, using "\" as an escape character. The subsequent JDBC driver execution also used ""\"" as an escape character
INC-148272 · Issue 609000
Increased specificity for collapsed DL
Resolved in Pega Version 8.4.4
When using the collapsible header functionality of a container skin format, the styling was not being applied correctly to the header. This has been resolved by increasing the specificity for a collapsed dynamic layer.
INC-149953 · Issue 613727
Increased specificity for collapsed DL
Resolved in Pega Version 8.4.4
When using the collapsible header functionality of a container skin format, the styling was not being applied correctly to the header. This has been resolved by increasing the specificity for a collapsed dynamic layer.
INC-186654 · Issue 669115
GetStatusChanges performance improvements
Resolved in Pega Version 8.7
Performance issues were seen when running the GetStatusChanges report. This was traced to the filtering methods used, and has been resolved by updating the report definition and enhancing the filtering conditions.
SR-A4720 · Issue 212436
Corrected focus for tabbing Ruleset inclusion data entry
Resolved in Pega Version 7.2
Data entry for "RuleSets To Include" was behaving unexpectedly when using keyboard-only input: when a value was entered in the "Minimum Version" text field, pressing TAB on the keyboard shifted focus from the next textbox to the top of the sheet due to a row-refresh added for app context. This has been corrected.