Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C91979 · Issue 431154

Null check added for Grid content in a read-only RTE

Resolved in Pega Version 8.3

The ui_grid.js was trying to initialize a grid from the markup of mail content. Since there were some missing attributes, script errors were thrown that resulted in an endless busy indicator. This is now fixed by adding the necessary null checks in Grid code.

SR-C93070 · Issue 431191

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-C89969 · Issue 431206

Webchat error fixed for Operator Template with User access role

Resolved in Pega Version 8.3

While running Webchat in an external application where the interface had any operator selected as an "Operator Template" with a User access role, the error "The chatbot is experiencing problems; If the issue is related to your current case, you can withdraw it by typing cancel" appeared. This was traced to an issue with creating/modifying instances of the class Data-NLP-Report-Summary, which is done in the Interaction API via pxSaveNLPSummary. To resolve this, the class has been added to the PegaRULES:User4 role so that any user access group can have write access to this class.

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us