INC-179167 · Issue 659592
Atmosphere update
Resolved in Pega Version 8.5.5
The Atmosphere jar has been updated to version 2.4.5.
INC-179448 · Issue 664314
Tracer protections updated
Resolved in Pega Version 8.5.5
Cross-site scripting protections have been updated for Tracer.
INC-182572 · Issue 663555
Support added for multiple host proxy architecture
Resolved in Pega Version 8.5.5
When using an architecture where certain types of users were sent through multiple proxy servers to get the Pega Cloud instance, an exception was generated at the point of accessing the environment. This was traced to the use of Apache 2.4 with mod_proxy. As the request passed through each proxy, the x-forwarded-host header had values appended to it by mod_proxy which resulted in the error "com.pega.pegarules.pub.context.PRSecurityException: Multiple host names in header X-forwarded-Host". This has been resolved by updating the code to support using a multiple host proxy configuration.
INC-184668 · Issue 665956
Check added for null mColumn values while estimating size
Resolved in Pega Version 8.5.5
A null pointer error indicating an issue with AbstractDataPageHandler.estimateDataSize was traced to missing handling for null values in mColumns while calculating size. This has been resolved with the addition of a null check.
INC-168254 · Issue 659299
Documentation updated for accents and special characters used in search
Resolved in Pega Version 8.5.5
The "Pega search API" article has been updated to reflect that the search functionality in Pega Platform does not match accented words with unaccented. For example, searching for santé and sante will retrieve different results. In addition, Domain Specific Language (DSL) includes special characters for use when searching, for example '-', '_', '!', '@'. However, the system retrieves various results depending on the way the special characters are used in the search query. If the query contains special characters that are not escaped, the system may retrieve incorrect results. For example, not escaping the slash mark in the 25/02 query may cause the system to ignore the special character.
INC-167606 · Issue 657153
Optimization prconfig check added for TableInformationMap
Resolved in Pega Version 8.5.5
A prconfig setting check has been added to the TableInformationMap use of OPTIMIZE_SMA_QUERY during its foreign key lookup.
INC-185758 · Issue 668961
Optimized GenerateID feature for case creation
Resolved in Pega Version 8.5.5
Enhancements have been added to support high-performance high-volume case ID generation on multiple databases including Oracle , MS-SQL, and Azure.
INC-170458 · Issue 667371
Handling updated for queue processor locks
Resolved in Pega Version 8.5.6
The Final activity mentioned in the processing epilog of the Service File rule was not being consistently called from File Listener, causing some of the cases to become stuck and not continue to the next stage. Investigation showed that if the lock was held by the queue processor requestor, the system was unable to obtain the lock but still proceeded to update the LogServiceFile page and persist it. This resulted in overwriting changes made on the LogServiceFile page by the requestor, resetting the completed-batches-count set back to 0. To resolve this, RuleServiceFile -> updateLSFBatchCounts() will call the overloaded lockAndLoad() method in LogServiceFile that accepts a parameter called lockAttempts. This will attempt to obtain a lock for a given number of times before throwing an exception.
INC-172849 · Issue 665981
SortPageList method updated for Obj-Sort
Resolved in Pega Version 8.5.6
Sorting page lists backed by a node level datapage using Obj-Sort was causing a ConcurrentModificationException. This has been resolved by updating the SorterImpl.sortPageList method to use java7CollectionsSort instead of collectionsSortWithInferenceEngineDisabled.
INC-173434 · Issue 672674
Pushservlet cookie path updated to resolve error
Resolved in Pega Version 8.5.6
A very large number of exceptions were being logged indicating "Unhandled error in web.request.internal.URLComponentProcessorImpl.populateCSRFToken", impacting the ability to perform log analysis. This exception has been resolved by updating the pushservlet cookie path.