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-B14774 · Issue 285008
Optional Process Child Case correctly sets ObjectClass
Resolved in Pega Version 7.3
When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.
SR-B14774 · Issue 285027
Optional Process Child Case correctly sets ObjectClass
Resolved in Pega Version 7.3
When creating a Child Case from an Optional Process on the Case Type Rule, the ObjectClass of WorkPage did not update to the object class of the child case. The proper class was set when generated using an Automatic Process on the ObjClass. This has been corrected by using a performAssignmentCheck before acquiring work object.
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-B36689 · Issue 292880
Performance improvements for CaptureInteraction without VBD
Resolved in Pega Version 7.3
CaptureInteraction was slow when not using a VBD server due to a call to the function GetVBDService that fired even when there was no intention to use VBD and it was not configured. This was an unintentional side effect of code that listens for VBD being ready in case it is in mid-initialization or cluster nodes are restarting. To improve performance, GetVBDService has been modified to avoid waiting for the VBD cluster if VBD is disabled using DSS prconfig/initservices/vbd/default = false.
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.
SR-A102729 · Issue 272707
Mobile modal display timing corrected
Resolved in Pega Version 7.3
When the full screen for mobile device option was used while launching a local action, the template buttons (Submit and Cancel) appeared to be missing until the screen adjusted during a focus shift to an editable field. This was an issue with asynchronous display timing in the modal dialog template using dynamic layouts with client side visible whens, and has been fixed.
INC-179478 · Issue 662927
Handling updated for progressive load on scroll in repeating dynamic layers
Resolved in Pega Version 8.7
When using progressive load on scroll on a repeating dynamic layout with a bar graph control, the bar which was loaded earlier was being removed during scrolling and only the current page's bar graph was displayed. This was traced to the page load and refresh handling in repeating dynamic layers, and has been resolved by modifying the logic to use a partial-refresh when appropriate.