INC-189477 · Issue 674034
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.7
While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.
INC-200029 · Issue 690167
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.7
While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.
SR-B12857 · Issue 285462
Repaired REST Connections with proxy
Resolved in Pega Version 7.3
After upgrade, connections to external internet websites/services were failing when using a proxy. This has been fixed.
SR-B33686 · Issue 295039
Repaired REST Connections with proxy
Resolved in Pega Version 7.3
After upgrade, connections to external internet websites/services were failing when using a proxy. This has been fixed.
SR-B37301 · Issue 295750
Repaired REST Connections with proxy
Resolved in Pega Version 7.3
After upgrade, connections to external internet websites/services were failing when using a proxy. This has been fixed.
SR-B6980 · Issue 278169
fixed naming in multiple extracts run from the command line
Resolved in Pega Version 7.3
When running multiple comma separated extracts at a time using command lineoption -i, all of the rules in the manifest file contained the value of the last extract name only. This was a missed use case, and ExtractImpl has been modified to correct it.
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-B35965 · Issue 302489
Fixed copy from data page with optional data mapping
Resolved in Pega Version 7.3
When 'Optional data mapping' was used on a pageList property with the 'copy from data page' option enabled, data was not getting populated to the PageList if the filtered result was page type. This was traced to an issue with optional data mapping in a keyed data page, and has been resolved by changing the function to add the indexed page instead of directly using the FilteredClipboardProperty.
SR-B16337 · Issue 287224
BIX TotalInserts and TotalInstance counts made consistent for nested pages
Resolved in Pega Version 7.3
The pxTotalInsertsCount and pxTotalInstanceCount values were being calculated incorrectly when using PageLists and a Page under those PageLists. This was a missed case, and the system has been updated to address it.
SR-B34230 · Issue 292359
BIX TotalInserts and TotalInstance counts made consistent for nested pages
Resolved in Pega Version 7.3
The pxTotalInsertsCount and pxTotalInstanceCount values were being calculated incorrectly when using PageLists and a Page under those PageLists. This was a missed case, and the system has been updated to address it.