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-B76668 · Issue 350935
Long pages print correctly in Microsoft Internet Explorer
Resolved in Pega Version 7.4
When using a print harness, long pages (width wise) were cut off when using Microsoft Internet Explorer. This was caused by Print preview getting scrolled, and has been resolved by adding a check in doc_lifecycle to return from the handling.
SR-A3011 · Issue 213185
Revised checksum to update imported rules
Resolved in Pega Version 7.2
When exporting updated rules after upgrade, a new rule in Data Transforms, Activities, and When was not being consistently used at runtime until the rule was resaved or the Virtual Rule Table Cache was regenerated. Beginning with Pega 7.1.8, a new property called pxSaveDateTime was added to rules. This new property is used in the checksum calculation to determine if a rule needs to be reassembled. However, when importing rules changed in pre-Pega 7.1.8 environments, the checksum calculation doesn't recognize the rule has changed. A change has been made to use pxUpdateDateTime as an alternative when pxSaveDateTime is not present in the rule.
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.
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-A10282 · Issue 222249
RD summarize menu context fixed
Resolved in Pega Version 7.2
When attempting to use Summarize functionality using a report definition, the Menu context page was not calculated properly due to an issue with the AggregateWrapper resolution of the input. This has been fixed.
SR-B79535 · Issue 331620
Logic updated for passing Connector DT param to Subflow
Resolved in Pega Version 7.4
Setting the parameter value through a Data Transform called on the Connector and then using it in a Subflow was resulting in the parameter value being blank in the Subflow. This was an issue with the passing of the parameter related to using CreateNewParamPage() in ProcessConnector FUA, and the logic has been modified to instead use tools.getParameterPage() when a Connector is using a DT.
SR-B90791 · Issue 339740
Autocomplete drop down selection supports Japanese characters
Resolved in Pega Version 7.4
When a text field of type autocomplete was set to a property holding Japanese text, the Japanese text appeared correctly in the dropdown displaying the choices but became garbled when one of the choices was selected. This was due missing support for Unicode characters in the method used for matching property names, and the regexp used in the replaceControlActionTokens API has been updated.
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-A5103 · Issue 214155
Improved Rule-Connect-SOAP connector performance
Resolved in Pega Version 7.2
Performance issues seen when running Connect-SOAP with NTLM authentication and tracing it using Performance Profiler have been resolved by modifying the parsing to improve use of the cached objects.