SR-C90853 · Issue 488536
Memory leak repaired
Resolved in Pega Version 8.3
A server side memory leak was traced to heap utilization increasing due to a Stream control assembly problem where the CleanForReuse() function was not cleaning up pzAuto. The cleanForReuse method in generated HTML properties is used to either initialize local fields, in which case aContext will be non-null, or to clear the object for pooling, in which case aContext will be null. Because the pzAuto variable was not being properly nullified, pooled controls were retaining stale references to StreamTools, LayoutRuntime, PRThread, and others. This has been resolved by adding code to ensure the pzAuto variable is correctly nullified.
SR-D12733 · Issue 488667
Code fragment removed to eliminate Fortify false positive
Resolved in Pega Version 8.3
A code remnant related to Boolean.getBoolean(..) in Rule-Declare testConsistency was causing a false positive in a Fortify scan. This piece of code is obselete and is not used anywhere, and has been removed.
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.