SR-D17568 · Issue 498410
Handling added for interaction portal refresh containing many data parameters
Resolved in Pega Version 8.2.3
Attempting to refresh the browser when there were interactions opened in the Interaction portal and a huge amount of data on the parameter page caused the screen to blank and the interaction content was not displayed. Investigation showed that as part of the refresh, the displayOnPage GET request was sent with all of the parameters in the parameter page (data-model), resulting in a 400 Bad Request due to the browser URL length limitations. This has been resolved by removing the parameters which are not actually required for the displayOnPage GET call during the refresh case.
SR-C95857 · Issue 483549
JSON parsing added for identifier data type
Resolved in Pega Version 8.2.3
After upgrade, Service-REST was no longer mapping data as expected when the property was of type "identifier". Handling has now been added for mapping where property type is identifier and the incoming type is any valid value for identifier.
SR-D11909 · Issue 488670
Secure and httponly attributes added to Pega-Perf cookie
Resolved in Pega Version 8.2.3
A vulnerability test identified the Pega-Perf cookie as not having any attributes for secure and httponly. This has been resolved.
SR-D14201 · Issue 485963
MY system pulse receiver will parse originating tenant name to facilitate data page removal
Resolved in Pega Version 8.2.3
When using a node level data page on a cloud multi-tenant system to get the data from a data table, attempting to flush the data page by explicitly calling pzFlushDataPage was not flushing the page in all nodes of a tenant. This was traced to the system pulse used to communicate between MT nodes: the receiver node was not removing the data even after receiving the system pulse because the cache contained the page with a different key. The key formed contained the tenant name, and the receiver was not parsing the tenant name from the pulse message received. To resolve this, the system has been updated to parse the tenant name from the pulse message and set it on requestor. This allows the correct key to be formed, allowing the receiver node to remove the data page as expected.
SR-D15391 · Issue 484922
Add row works as expected when using Embedded Elsewhere with a modal grid
Resolved in Pega Version 8.2.3
When using Embedded Elsewhere, add row was not working on the first attempt for a grid launched inside a modal dialog. Changing the focus then resulted in the added row appearing. This has been resolved by updating the timing for the performInsertAction in the ui_grid JS.
SR-D20817 · Issue 499920
Async cache checking updated for interaction reload use
Resolved in Pega Version 8.2.3
A thread level data page using connect REST to get data from an external system with the "Reload once per interaction" checkbox ticked was being loaded asynchronously from the activity when by default the data page it was supplying needed to be loaded synchronously. Due to this, changes to the data in the external database were not reflected in the data page. This was caused when an async cache was referred and the freshness check for the data page instance did not consider the 'reload once per interaction' flag because it would cause the data page to load twice. The cache checking has been updated to resolve this.
SR-C95733 · Issue 444477
SendSimpleEmail modified to show complete attachment subject line
Resolved in Pega Version 8.2.3
The complete subject of the correspondence attached in a work object was not displayed in the UI. The clipboard page pyWorkPage -> Attachment (Link-Attachment) also showed an incomplete value in the pyMemo property, displaying only 64 characters. Investigation showed that pyCorrPage.pyLabel was being set to 64 characters in the Work-.SendSimpleEmail activity, and then used LinkMemo to show the value in the UI. To resolve this, the system will take HistMemo as the LinkMemo as well if it is available and then truncate it to the Link-Attachment.pyMemo size to store the entire value as exposed.
SR-C96552 · Issue 488911
WordMacroManager updated to support both 32-bit and 64-bit
Resolved in Pega Version 8.2.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-C97046 · Issue 485715
Added restriction to limit environment sending multiple OTP emails
Resolved in Pega Version 8.2.3
Multiple One Time Password (OTP) Emails were being sent for a single requestor on a change password screen when the password was expired. This was caused by the environmental settings refreshing the changepassword harness, and has been resolved by adding a restriction against sending multiple OTPs for a requestor to whom an OTP has been successfully sent once.
SR-D10666 · Issue 490865
InitializeRequestor utilized to prevent Inconsistent authentication requestor state
Resolved in Pega Version 8.2.3
A 'resource not found' issue was causing an inconsistent Robot status. This was traced to an improperly configured application where the service authentication requestor was left in a wrong state but was being returned to the pool. To prevent the issue of requestors being in an odd state if they try to authenticate and an error occurs, the system has been updated to now always call initializeRequestor, not just for Authenticated cases.