INC-147873 · Issue 610865
Custom header character encoding for Subject added
Resolved in Pega Version 8.5.5
Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers.
INC-161645 · Issue 634639
Java Bean import updated to handling differences in Java 7 and Java 8
Resolved in Pega Version 8.5.5
The behavior of the java bean Introspector class is inconsistent across different versions of the JDK when detecting indexed properties built off of java.util.List objects, causing Java Bean import to generate differently in Java 7 and Java 8. This has been resolved by updating PRIndexedPropertyDescriptor to better handle this JDK difference by resolving indexed read and write methods manually using simple reflection.
INC-163292 · Issue 635839
Portlet service deprecated
Resolved in Pega Version 8.5.5
Portlet authentication services have been removed from the standard installation package. The IAC service has been restored.
SR-D32381 · Issue 519465
Transient property passivation handling improved
Resolved in Pega Version 8.2.6
Frequent "com.pega.pegarules.pub.PRRuntimeException" errors were seen in the production log file while working on the WO. This was traced to corruption in the blob caused by transient properties during passivation. To resolve this, corrections have been made to the handling for the transient property entries in the blob.
SR-D41229 · Issue 513589
Enhancements added for using AWS file repositories
Resolved in Pega Version 8.2.6
Enhancements have been added to improve the use of AWS file storage: - Logging for AWS SDK connection metrics can be activated on a per-repository basis, either through the ruleform or through the DSS `storage/class/:/enableMetrics`. - INFO logging can be enabled on PegaAWSSDKMetricReporter to periodically output averages of recorded metrics for all registered S3 repositories with metric collection enabled, or INFO logging can be enabled on PegaAWSRequestMetricCollector to output recorded metrics on every client call for all registered S3 repositories with metric collection enabled. - The interval at which PegaAWSSDKMetricReporter logs metrics at can be configured with the DASS `storage/AWSSDK/metricReportingInterval`. This DASS is a system-wide setting, and not a per-repository setting. The default reporting interval is 90 seconds, and metric collection is disabled on all repositories by default.
SR-D42241 · Issue 518639
CyberArk support has been added for this release
Resolved in Pega Version 8.2.6
CyberArk support has been added for this release.
SR-D43740 · Issue 514124
Added support for Helper Text Question Mark with visibility condition
Resolved in Pega Version 8.2.6
The Helper Text Question Mark was not displaying if the control was configured with "Help icon with overlay on hover" combined with a visibility condition. This was a missed use case, and the expression visibility support for controls.changes have now been added in the pzpega_ui_DLCellTemplate.js file.
SR-D45622 · Issue 521661
Sorting on Grid works with declare expression property
Resolved in Pega Version 8.2.6
If a property with a declare expression was used in a column, the sorting on that column was not working. This was traced to reference errors when Grid used the engine API pega.sortPageList to sort the page list / data page, and has been corrected.
SR-D47484 · Issue 516149
Added visibility to dropdown for change stage
Resolved in Pega Version 8.2.6
While creating a flow in work- class that used a change stage, on selecting 'other' the dropdown to show other stages was not visible. This was due to a missing visibility condition, and has been resolved by updating "pzPopulateStages" Step7 to set the pyGotoStageOther to "OTHER" when none of the stages are present.
SR-D51725 · Issue 516467
DSS added to rpevent logging of sensitive data used as input during async batch task processing
Resolved in Pega Version 8.2.6
When running Async Batch Task Processing, the whole set of inputs was logged when an error occurred during ADP load. Because this might result in sensitive data such as SSN, DOB, IDs, etc, being included in the debugging output, a DSS has now been added which when set will avoid printing any sensitive information in the log.