SR-C93070 · Issue 431218
Fixed Export to PDF page formatting
Resolved in Pega Version 8.3
A formatting issue was seen when using export to PDF; the first page contained only the title of the report as well as the filter, the generated date, and the number of records, and the exported data was included only from the 2nd page onwards. This has been corrected, and some performance improvements for the generation time were added.
SR-C93344 · Issue 431347
Bcrypt password hash increased to 2^12
Resolved in Pega Version 8.3
Bcrypt password hashes have been increased to 2^12 iterations for new passwords.
SR-C91927 · Issue 431508
ValidateSurveyStream updated to ensure validation runs on a named page
Resolved in Pega Version 8.3
After creating new survey rules, trying to re-validate and save in survey-specific rules was failing to re-validate in standard/personal edition. This was an issue with the ValidateSurveyStream activity running on an unnamed page: in this activity, the stepPage name is set to a parameter and passed to datatransform for the processing of the rule. Since the steppage was unnamed, an exception was thrown. To resolve this, steps have been added in the ValidateSurveyStream activities for question, question group, and survey that will copy the primary page into the named page and pass it as a parameter.
SR-C93506 · Issue 431515
Prconfig enhancements for Cassandra diver connection pool
Resolved in Pega Version 8.3
An enhancement has been added to to support the following prconfig setting options for the Cassandra driver's connection pool:dnode/cassandra_max_requests_per_connection/local dnode/cassandra_max_requests_per_connection/remote dnode/cassandra_max_connections_per_host/local dnode/cassandra_max_connections_per_host/remote In addition, error handling in the CassandraBrowseByKeysOperation has been improved. To avoid NPEs caused by a record in Cassandra (DDS data set) that has data_ column set to null, CassandraDataEmitter will skip records with a null data_ column.
SR-C93555 · Issue 431598
BulkMover updated to not treat Numerics as strings
Resolved in Pega Version 8.3
When attempting to update Pega platform 8.1.1 to 8.1.3 with Oracle on a Windows machine with German locale using the out-of-place upgrade of the rules schema, the migration failed at the migration step with the error message "ORA-01722: Ungültige Zahl". This was traced to BulkMover failing when trying to convert a string to a Numeric due to the locale using commas as the decimal separator, and has been resolved by updating BulkMover to not treat Numerics as strings.
SR-C87757 · Issue 431643
Country Code for Austria saved correctly
Resolved in Pega Version 8.3
When trying to save an address with CountryCode=AT, the code was saved as "at" instead. This was caused by a temporary field value not being correctly cleared, and has been resolved.
SR-C86138 · Issue 431775
Security updates for avatar upload function
Resolved in Pega Version 8.3
Updates have been made to enhance security around the avatar upload function.
SR-C79017 · Issue 431816
Metadatatree updated to be function-scoped in UI to resolve custom tab control display issue
Resolved in Pega Version 8.3
When switching rapidly between two custom tabs, especially clicking in and then clicking away before the busy icon could be displayed, the section containing the tab controls was intermittently refusing to display. Refreshing the browser or clicking on the Pega button made the section visible again. This was traced to the template "metadatatree" getting overlapped with subsequent template processing due to a timing issue as "metadatatree" was being maintained in the global window object. To resolve this, "metadatatree" has been updated to be function-scoped in renderUI to avoid timing issues.
SR-C89954 · Issue 431930
Rule-Connect-SOAP error fixed for WAS/JBOSS environments
Resolved in Pega Version 8.3
After upgrade, SOAP webservice was failing with the error “Couldn't create OMElement from string value for the activity InvokeAxis2 in class Rule-Connect-SOAP". This occurred on sites using a WebSphere/JBoss environment, and was traced to an issue where the WAS classloader was loading its default jar at the same time the Pega classloader was loading the same jar into JVM. This has been resolved.
SR-C89716 · Issue 431990
Rule-Connect-SOAP error fixed for WAS/JBOSS environments
Resolved in Pega Version 8.3
After upgrade, SOAP webservice was failing with the error “Couldn't create OMElement from string value for the activity InvokeAxis2 in class Rule-Connect-SOAP". This occurred on sites using a WebSphere/JBoss environment, and was traced to an issue where the WAS classloader was loading its default jar at the same time the Pega classloader was loading the same jar into JVM. This has been resolved.