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.
SR-A16535 · Issue 231740
Null Boolean and datetime properties passed in command line extraction
Resolved in Pega Version 7.2.1
If a Boolean or a datetime Embedded valuelist /valuegroup /pagelist/page group property was in the WO blob but has no value when extracted from the command line using the -B and -J options, the value in the extract was not valid. This was traced to the handling for empty Boolean and datetime properties, and these properties will now be passed without modification when using the command line options -B and -J in XML output format or when running the extract from the UI.
INC-167388 · Issue 651309
Values treated as strings for offline data transform concatenate
Resolved in Pega Version 8.7
When using a Data Transform to construct a URL using multiple properties that contain values with a leading or trailing "0", the "0" was trimmed when the corresponding mobile JS code was generated using pega.process.expression.getValue("pyWorkPage.PlanData.SegmentID", "pyWorkPage.PlanData") . This was traced to the offline property type assuming that any numbers-only string should be treated as a number, so the data transform concatenate was converting “0001” to 1. To resolve this, the value will be treated as a string when being evaluated in an offline data transform.
SR-A16904 · Issue 234334
Wrapper added to expression builder for the jump transition on a step
Resolved in Pega Version 7.2.1
While using expression builder, selecting the option for "Enable conditions after this action" in an activity and submitting the expression did not show the expected result in the When input box. Attempting to use the expression builder again and submitting it then resulted in the screen freezing and requiring a refresh. To resolve this, a "pyStepsTransSection" wrapper section was been added for the "pyStepsTransParamsWhen" when condition.
INC-184729 · Issue 669741
Pinning document to space correctly generates thumbnail
Resolved in Pega Version 8.7
When pinning a document to a space using the standard document repository tile, the resulting pin did not have an image corresponding to it. The process worked properly when pinning a document directly from the space itself. This was a missed use case and has been resolved by adding an update to set the pyImage of the document while pinning the space.