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-A93912 · Issue 261494
SSLUtils modified to support app container keystore/truststore
Resolved in Pega Version 7.2.2
Keystore and truststore configured at application container level were not being used by SOAP Connectors. To facilitate use, when SSL settings are not provided at a rule level SSLUtils will create a wrapper around the Java default SSL artifact and use that.
SR-A93912 · Issue 264848
SSLUtils modified to support app container keystore/truststore
Resolved in Pega Version 7.2.2
Keystore and truststore configured at application container level were not being used by SOAP Connectors. To facilitate use, when SSL settings are not provided at a rule level SSLUtils will create a wrapper around the Java default SSL artifact and use that.
INC-139260 · Issue 592218
Handling added for third party form library
Resolved in Pega Version 8.5.2
When using a third party library which created a form tag, the wrong form was used on submit in the Ajax container. This has been resolved by updating the pzpega_ui_doc_submit file submitInner method to handle this use case.
INC-139260 · Issue 592219
Handling added for third party form library
Resolved in Pega Version 8.6
When using a third party library which created a form tag, the wrong form was used on submit in the Ajax container. This has been resolved by updating the pzpega_ui_doc_submit file submitInner method to handle this use case.
SR-118125 · Issue 171188
Circumstance property value carried into dropdown options
Resolved in Pega Version 7.1.7
If a property of mode single value and type text was created with a defined local list of property values for the property, the value field was not automatically included in the dropdown options when attempting to use this property for circumstance/specialized flows. This was caused by an incorrect refresh section strategy used to determine when to reload the section for the circumstance by property, and has been corrected.
INC-139095 · Issue 596507
Portal loads for Simplified Chinese locale in IE
Resolved in Pega Version 8.5.2
When using IE, the portal would not load when using the Simplified Chinese locale. This was caused by Microsoft Internet Explorer rendering the locale as 'zh-CN-#Hans' instead of the expected 'zh-cn'. This has been resolved by adding a check to remove the "#" in the locale string to avoid a malformed URL.
INC-149823 · Issue 608353
DX API returns properly referenced icon class for embedded page
Resolved in Pega Version 8.6
When using the DX API to build an Angular JS UI, the response returned from the GET /cases/{ID}/actions/{actionID} api did not return the iconStyle for an icon class that uses a property reference when the flow is on an embedded page. This has been resolved by adding code to set the correct context for pzAPICreateJsonForModes and pzAPICreateJsonForField RUF.
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.