INC-187553 · Issue 675429
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-188080 · Issue 673783
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-188143 · Issue 674972
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-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.
INC-157448 · Issue 638925
Latitude and longitude populated for CreateWork history
Resolved in Pega Version 8.7
After enabling geo location in the casetype rule, when the case was created using the Create menu option from either Dev studio or Manager portal the Latitude and longitude values were set on the pxRequestor page and were available in the Case Audit history in the Map control. When the same case was created using CreateWork action configured on a button, it did not log the latitude and longitude values in the case Audit history. Investigation showed this was caused by a 'when' condition in the AddWorkHistory activity which checks the requestor page for latitude value and which had a null value when a createWork action was used to create the case. To correct this, the template metadata of the form will be populated with latitude and longitude values from pxRequestor page to be used in the latitude and longitude hidden fields.
SR-A23050 · Issue 244774
Rule generation updated to handle related JSONs
Resolved in Pega Version 7.2.1
The system was failing to parse inbound JSONs when the corresponding Pega Data Model was generated using the same JSON, and was unable to use valuelist or pagelist properties for generating JSON to pass to connect-Rest Method. This generation and runtime of rest connector was failing when the same name property existed in multiple places with different modes and same levels. To support this use, the rule generation has been updated to correctly populate the qualifier name along with modified run time code to support mapping when same properties are there in the same class.
SR-A19704 · Issue 234771
Refresh list action retains focus on work area
Resolved in Pega Version 7.2.1
When used as used as part of enabling successive rows, the refresh list action was returning focus back to first item rather than holding focus at the working point. This was found to be caused by a ?Select first row on initial load? option when ?Refresh List? is performed, and this code will no longer be called in this scenario.
SR-A21043 · Issue 241137
Refresh list action retains focus on work area
Resolved in Pega Version 7.2.1
When used as used as part of enabling successive rows, the refresh list action was returning focus back to first item rather than holding focus at the working point. This was found to be caused by a ?Select first row on initial load? option when ?Refresh List? is performed, and this code will no longer be called in this scenario.
SR-A18716 · Issue 234856
Corrected Hotfix Manager mismatch between 7.2 versions
Resolved in Pega Version 7.2.1
The version of 7.2 used in the Hotfix Catalog was different from the version used in Hotfix Manager when installing DLs. An update to the HM code was made to correct this mismatch.