SR-D13450 · Issue 488138
Corrected Query logging level for Populate_UsepxRequiredSkillsCount
Resolved in Pega Version 8.3
A Query was being logged with Logging level of Error in pzPopulate_UsepxRequiredSkillsCount. This has been corrected.
SR-D18814 · Issue 488259
Enhancement added to fetch HTML attachment from CMS
Resolved in Pega Version 8.3
When email containing HTML was sent to the Listener, some of the characters were not getting decoded properly when viewing. In this case, HTML email content was saved as an attachment in CMS , and this error was traced to the system being unable to fetch the attachment. To resolve this, an enhancement has been added to fetch non-Pega database attachments using pxGetFileAttachmentContent.
SR-D1270 · Issue 488261
database table mapping will check for existing properties before creating them
Resolved in Pega Version 8.3
Using the Database table class mapping tool to map an external database table to a class and create properties according to columns in the table was resulting in the property being created as 'not available' and not case sensitive if the property to be created while mapping was already present in the inheritance hierarchy. This led to an error caused by the property validation failing in the validateReportDesignTab activity. Previously the database table mapping tool did not check to see whether the properties to be created existed already in the parent class hierarchy. With this update, the system will check before allowing the mapping, and if the properties exist in the hierarchy already they will not be populated.
SR-D14601 · Issue 488290
Unique ID generation added for simultaneous multiple text area boxes
Resolved in Pega Version 8.3
In the Interaction portal, adding a task for a interaction using a form with a character-count enabled text area worked as expected when the interaction first opened a task with the character counter text area. However, if a second version of the same task was opened before the first task was completed, the second text area was not responsive or working as expected. This was traced to the system generating the same ID attribute for both instances of the text area character counter span, and has been resolved.
SR-D19944 · Issue 488359
Search initialization logic updated to ensure consistent node member information
Resolved in Pega Version 8.3
The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.
SR-D19945 · Issue 488360
Search initialization logic updated to ensure consistent node member information
Resolved in Pega Version 8.3
The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.
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.