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-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-150172 · Issue 611774
Updated class handling for View field security
Resolved in Pega Version 8.4.4
When using a defined View which returned a page and its fields and used an inherited custom work party definition, trying to update the pyWorkParty(Customer) by calling the "post /assignments/{ID}/{actionID}" did not work as expected when Field Security was ON. This was traced to the field security relying on the design time page class information stored in the list/group property, and has been updated to resolve the view fields using actual class information from the work page.
SR-A93593 · Issue 260733
Cross Origin mashup request fixed for Microsoft Internet Explorer /Safari
Resolved in Pega Version 7.2.2
When the mashup code hosted in domain1 was trying to access the PRPC content hosted in domain2, it failed when using Microsoft Internet Explorer and Safari but worked in Google Chrome. For a HTTP request whose response status is 303, the response headers given using Dynamic system setting "http/responseHeaders" were not being sent. This has been corrected.
SR-A92015 · Issue 260437
MobileSnapStart portal works with OpenWork
Resolved in Pega Version 7.2.2
When using pyMobileSnapStart and openWorkByHandle, the portal was displaying along with the case. However, any portal action that went through OnDesktopAction failed even though actions within the case were working. This was an issue with Portal actions not working when using openWork, and has been fixed with an added null check for docsRecreateInfo in dynamiccontainer_lite js to handle pyMobileSnapStart cases.
INC-149823 · Issue 608352
DX API returns properly referenced icon class for embedded page
Resolved in Pega Version 8.5.2
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 Rule-Utility-Function.
INC-149823 · Issue 608354
DX API returns properly referenced icon class for embedded page
Resolved in Pega Version 8.4.4
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 Rule-Utility-Function.
INC-142084 · Issue 599875
Support added for expression in strategy scorecards
Resolved in Pega Version 8.5.2
When invoking REST against a dataflow that had a strategy containing a scorecard that used an expression and the "Include model explanations option" was enabled in the Strategy configuration, the system failed with the error "PropertyValueInvalid .pxMaxScore Cannot cast the value (unknown) to double". This was traced to the Scorecard explanations failing during serialization when an expression was used, and has been corrected.
INC-142084 · Issue 599877
Support added for expression in strategy scorecards
Resolved in Pega Version 8.4.4
When invoking REST against a dataflow that had a strategy containing a scorecard that used an expression and the "Include model explanations option" was enabled in the Strategy configuration, the system failed with the error "PropertyValueInvalid .pxMaxScore Cannot cast the value (unknown) to double". This was traced to the Scorecard explanations failing during serialization when an expression was used, and has been corrected.