SR-D11909 · Issue 488671
Secure and httponly attributes added to Pega-Perf cookie
Resolved in Pega Version 8.3
A vulnerability test identified the Pega-Perf cookie as not having any attributes for secure and httponly. This has been resolved.
SR-D18286 · Issue 488801
Information on operator disablement clarified
Resolved in Pega Version 8.3
The Security Policy settings referred to in http://doc-build02.rpega.com/docs-oxygen/index.htm#security/security-policies/sec-security-policies-settings-ref.htm#security_policies_settings_ref have been updated to clarify the information on operator disablement.
SR-D18907 · Issue 488899
Property references now supported for label and checkbox captions
Resolved in Pega Version 8.3
An enhancement has been added to support the use of a property reference for labels and checkbox captions.
SR-C96552 · Issue 488912
WordMacroManager updated to support both 32-bit and 64-bit
Resolved in Pega Version 8.3
After upgrade, the FlowAction=> CreateMergedWordDoc was not working. This was traced to Word Merge failures due to 64-Bit incompatibility with the WordMacroManagerDot template file, and has been resolved by updating WordMacroManagerdot.dot so it supports both 32-Bit and 64-Bit.
SR-D20791 · Issue 489023
Support added for section completion of nested page list/groups in DX API
Resolved in Pega Version 8.3
When using DX API and submitting a screen from the front end which was in an embedded section, "Pega_API_001" errors appeared. An enhancement has now been added to support completing the fields in an embedded section by updating the system to handle nested page lists/groups and updates to "newRow" for nested page lists/groups.
SR-D17907 · Issue 489173
Resubmit task now moves partitions to end state before restarting
Resolved in Pega Version 8.3
Resubmitting a failed task did not put the partitions into an end state, resulting in queue processor failure that did not automatically restart as expected. This has been fixed by modifying the resubmit task to move partitions to end state.
SR-D16884 · Issue 489355
Added handling for cases where Microsoft Internet Explorer causes a SAXParseException
Resolved in Pega Version 8.3
Numerous SAXParseException messages were seen in the log file, and the queryString showed the pyDeleteDocumentPg being referenced. This was traced to the method used by Internet Explorer to construct an HTTP request: Microsoft Internet Explorer sends the header and body of the request in separate TCP packets, but for an unknown reason in this case the body packet goes missing. To resolve this, a toggle has been introduced which will send the pyDeleteDocumentPg request as GET if pega.u.d.GET_REQUEST_DELETEDOCUMENT is set to true in userworkform. In a normal flow without this variable, the request will pass through the normal flow.
SR-D18209 · Issue 489547
Check added to avoid unnecessary show-harness when offline
Resolved in Pega Version 8.3
After upgrade, clicking on the Optional Process from the Action menu resulted in the error "The Operation completed successfully, but returned no content". This was traced to an unnecessary call to a show-harness step when offline, and has been resolved with the addition of a 'when' check.
SR-D17318 · Issue 489605
Enhancements added to Proposition Filter
Resolved in Pega Version 8.3
Previously, when propositions were filtered based on only specific criteria, then propositions based on both the specific and default criteria were shown. An enhancement has been added to address this, as well as to create a better user experience for the proposition filter with a simpler UI and some additional features. In this revision, there is one data model that supports the platform proposition filter as well as Pega marketing's eligibilities. The condition builder is used in the Proposition filter rule to align user experience with marketing, and the new proposition filter supports parameters for when rules. DMSample contains an example proposition filter rule that uses and showcases the new UI, including available values.
SR-D15495 · Issue 489736
Function in aggregate filter condition properly displayed
Resolved in Pega Version 8.3
After constructing a report definition with Filter conditions to apply after the aggregation filters with max as function, the function was not visible in the dropdown when the rule was opened. The Function was visible if the rule was checked out and remained visible if the checkout was discarded, but if the rule was opened and closed again the max function was not visible. This was traced to the Primary page not being considered properly while populating the data page D_pzGethavingFilterFunctions which loads the options for the filter dropdown. To resolve this, the activity pzHavingFilterFunctions has been modified to check for pzPrimaryHarnessPageName first before pzPrimaryPageName.