INC-161645 · Issue 634637
Java Bean import updated to handling differences in Java 7 and Java 8
Resolved in Pega Version 8.4.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-161838 · Issue 631912
GRS support added to Display name and Reply to for SendEmailNotification
Resolved in Pega Version 8.4.5
After upgrade, it was not possible to send email notifications when using a Datapage property in the email account rule. Investigation showed that there was a custom activity being used to call the SendEmailNotification activity and set the pyNotifyAccountName value as email account name by enabling Pass current parameter page, and the custom call was not functioning due to the SendEmailNotification activity being completely refactored in recent versions of the platform where GRS support (which was not a documented feature) was removed. For better backwards compatibility, this issue has been resolved by adding GRS support to Display name (pyFromFullName) and Reply to (pyReplyTo).
INC-161952 · Issue 645674
Race condition resolved for input/output pipe streams
Resolved in Pega Version 8.4.5
Writing to S3 using file data set was failing with the error "Exception occurred while uploading file". The system was relying on PipedInputStream for getting the data from the file while uploading, which needs to be connected to PipedOutputStream which holds the data to be uploaded. Investigation showed a race condition was occurring where for some use cases the reading of inputStream was happening before the connection of I/P and O/P streams, resulting in a "Pipe not connected" error. This has been resolved.
INC-162198 · Issue 628702
Tracelist cleared to address parser exception in REST Service
Resolved in Pega Version 8.4.5
In a requestor pool of mixed types, HTTP and REST, the alert data was not initialized properly if there was a parse exception due to invalid data in the incoming payload. For example, last_input, first_activity, and last_step could all be left over from the prior HTTP service request. This was caused by the system pulling in seemingly unrelated activities for the "Last activity called" in the stack trace of a service when a single alert was created by two different service types which were sharing the same package, and has been resolved by explicitly clearing the tracelist for the service to prevent inaccurate information being reported in the logs.
INC-162217 · Issue 635888
Default sorting with Pagination, Data Page and Report Definition corrected
Resolved in Pega Version 8.4.5
After configuring a section with the table sourced from a data page and personalizing the table with the pagination and sort-by features available in a report definition, the table content sourced with the data page was not sorting the data. This has been resolved by updating the pxRetrieveReportDefinition activity so that the sort order for queryable data pages will not be reset for a first-time request.
INC-162987 · Issue 640145
Cross site scripting protections updated for SOAP WSDL
Resolved in Pega Version 8.4.5
Cross site scripting protections have been updated for reading WSDL nodes.
INC-163863 · Issue 632424
Monthly agents run correctly on non-English locales
Resolved in Pega Version 8.4.5
Nodes with non-English locales were not starting when using an Agent with a monthly execution pattern. This was due to incorrect handling of the user locale, and has been resolved.
INC-163985 · Issue 635144
Class mapped to CustomerData is incrementally indexed as expected
Resolved in Pega Version 8.4.5
When using a class which mapped to customerdata, instances that were added/updated were not automatically getting indexed unless a full reindex was performed. If the class mapping was changed from customerdata to pegadata then the incremental indexing was done. To resolve this, the UpdateProcessor class that resolves CustomerData to the correct database name has been updated to use PegaData. ConfigurationMapImpl contains the resolution mapping and a call is made to ConfigurationMapImpl to retrieve the correct database name.
INC-164021 · Issue 638637
Java object type removed from pyStream to resolve GetFile class error
Resolved in Pega Version 8.4.5
It was not possible to perform Property-Set on pyStream(java.io.InputStream) to assign it with another object of type(returned by pxGetFile Rule-Utility-Function). This was caused by a strongly typed java.io.stream in the pyStream property creating conflict at runtime with S3WrapperInputStream from the D_GetNewFile call, and has been fixed by removing the java object type from pyStream.
INC-164308 · Issue 634408
UseNoCacheHeaders default expiration set to "0"
Resolved in Pega Version 8.4.5
When the prconfig/HTTP/UseNoCacheHeaders/default was set true it used the value "Expires: Thu, 01 Dec 1994 16:00:00 GMT". This has been updated to the more commonly used setting "0".