INC-139695 · Issue 593085
Mountain timezone format updated
Resolved in Pega Version 8.3.5
If an operator was created with any calendar instance timezone mapped to "Canada/Mountain" and made unavailable for the current period, routing an assignment to that operator using the standard ToCurrentOperator activity resulted in a null pointer error when the Rule-Utility-Function was executed to find a substitute operator. This was traced to the timezone format Input to DateTimeUtils API (parseDateTimeString) having the wrong timezone, for example, 20200819T080000.000 MDT (CA), and has been resolved by modifying the locale XMLs to remove (CA) from zone code so that MDT (CA) is updated as MDT.
INC-141299 · Issue 593305
PRTraceServlet security check added
Resolved in Pega Version 8.3.5
Modifying the Pega application URL with PRTraceServlet displayed multiple user credentials and session information. This has been corrected with the addition of a privilege check in GetConnectionListCommand before allowing the connections list to be fetched.
INC-127420 · Issue 568438
Requestor details shown in Pr_perf_stats table
Resolved in Pega Version 8.3.5
When using a Custom table with the requestor details inserted in the ApplicationSetup activity, comparing the passivated requestors from standard table Pr_perf_stats showed that sometimes requestor details were not present in table Pr_perf_stats. This was traced to the the column value for standard table being greater than the column value for the columns pxDecryptCount, pxDecryptCPU, pxDecryptElapsed, pxEncryptElapsed, pxEncryptCPU, and pxEncryptCount. Database numeric column size is (9,6) whereas other numeric columns have size (18,6). To resolve this, the table scripts have been modified to increase the column size from (9,6) to (18,6).
INC-146057 · Issue 599808
Secure access for Activitie
Resolved in Pega Version 8.3.5
Authentication requirements have been added to Standard activities.
INC-128250 · Issue 571240
Validations and rules tuning
Resolved in Pega Version 8.3.5
Issues relating to an extra row being added to auto-populated properties, adding a 'when' visibility to a picklist property, and errors saving nested properties have been resolved, and performance of the overall system has been improved.
INC-137235 · Issue 586081
Validations and rules tuning
Resolved in Pega Version 8.3.5
Issues relating to an extra row being added to auto-populated properties, adding a 'when' visibility to a picklist property, and errors saving nested properties have been resolved, and performance of the overall system has been improved.
INC-144601 · Issue 602424
Empty addresses removed from email
Resolved in Pega Version 8.3.5
After upgrade, an issue was seen when sending email to multiple 'To' addresses generated an exception if any 'To' address had an empty value. To resolve this, a check has been added that will remove any empty address from the recipientTo address list.
INC-143622 · Issue 602980
Improved privacy for email listener alerts
Resolved in Pega Version 8.3.5
To improve privacy, the customer 'from' address will be removed from PEGA0011 alerts for email listener processing.
INC-130176 · Issue 585374
Removing PageList removes all cached pages
Resolved in Pega Version 8.3.5
A previous change was made such that when removing a pageList property, its size is removed from the size-specific cache as well. A further enhancement has been made so that when a PageList is removed, the system will clear the pageCache of all cached pages in the PageList.
INC-133583 · Issue 584923
Rest connector supports extended chars in attachments
Resolved in Pega Version 8.3.5
When the pyRequestAttachmentPage clipboard page was populated with a file name that contained Latin supplemental 1 unicode characters (decimal values 160 to 255 - for example an umlaut), any extended characters were being converted to question marks (?) before the call was sent, causing the web service call initiated by Pega to fail. To better support this use, an enhancement has been added to support a multipart request with extended characters in the file name. This allows the pyRequestAttachmentPage to specify pyFileNameExtendedChars, allowing RFC 6532 mode to be toggled for multipart requests with attachments. This mode allows for UTF-8 encoding in the attachment file name header, rather than the default ASCII encoding.