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-A92 · Issue 203202

Removed extra slash character being appended in prconfig

Resolved in Pega Version 7.1.9

When configuring prconfig settings, an extra slash was getting appended when the sethtmlbasecontext had trailing slash in the URL. This has been corrected.

SR-A955 · Issue 204118

Fixed typo in error message

Resolved in Pega Version 7.1.9

A typo in an HA status message written to the log has been corrected.

SR-A1273 · Issue 197681

PRPCTask is now tenantized

Resolved in Pega Version 7.1.9

On a multi-tenant environment with HTTP event, it was not possible to see the options for warm\blind transfer with interaction from a tenant layer. This was an issue with the task taking the user ID information but not taking the tenant information, so the acceptance of the interaction on the portal was not getting delivered to the desktop. To correct this, PRPCTask is now tenantized.

SR-A3149 · Issue 209034

Added handling for Oracle functional indexes of length '1'

Resolved in Pega Version 7.1.9

The SchemaChangeUtils class was throwing a java.lang.StringIndexOutOfBoundsException when an administrator attempted to view the "Missing PRPC Shipped Schema" section of the "PRPC Schema Report" page after upgrade (System -> Release -> Upgrade -> PRPC Schema Report). This appeared to lead to the message "Can not render section" in the PRPC schema report UI. The StringIndexOutOfBoundsException was due to Oracle functional indexes of length '1' which were not handled while doing a substring in schemaChangeUtils class: this handling has now been added.

SR-A34 · Issue 204505

Pega Lookup JSP tag correctly retrieves Chinese characters

Resolved in Pega Version 7.1.9

When the pega:lookup JSP tag did a field value lookup on pyCaption to retrieve the field value consistent with the locale, any Chinese characters embedded in the HTML pages used to generate the PDF rendered correctly but '?????' appeared in the PDF content instead of the Chinese characters configured in the Field-Value pair. This was caused by an issue in the code which caused the system to incorrectly identify NVARCHAR columns as being VARCHAR columns. This has been fixed., and the encoding for TestDatabaseNew has also been set to be UTF-8 to ensure the Non-ASCII characters in the tests are handled properly in all workspaces.

SR-A3428 · Issue 212424

Modified ClassName pass method for external DBs

Resolved in Pega Version 7.1.9

When DB2 is used as external DB (external table has a date column) and PRPC is hosted on a DB other than DB2, performing an obj-save into an external DB2 database failed with an SQL error. This issue occurred when a class was mapped to a table in an external DB which was not same as Pega hosting DB. In class PageDatabaseMapperImpl.java , function getDatabaseTypeFromEngine is used to check the database type when column type is Date, but the function was using a hardcoded value of class to determine the database type. This has been changed to pass className as parameter and use it to determine database type.

SR-A3744 · Issue 209253

Resolved Vtable NPE during engine start

Resolved in Pega Version 7.1.9

If a Rule-Access-When was defined on the class Data-Admin-System-Settings, search was initialized before the VTable is initialized. While initializing search, a DASS was set and a save operation was performed on the DASS which then tried to perform a security check and attempted to retrieve the Rule-Access-When from the unpopulated VTable cache. This led to an NPE. To resolve this, changes have been made so that search will be initialized after Vtable is populated.

SR-A940 · Issue 205402

Locking issue resolved for importing PUI jars

Resolved in Pega Version 7.1.9

Errors were being generated when importing PUI framework jars. This was an issue where the savepoints created in Saver.executeUpdate needed to be explicitly released on PostgreSQL to avoid locks from accumulating for each of the nested transactions, and the problem has been resolved.

SR-A990 · Issue 205075

Post-upgrade deferred list mapping reference inserted for new classes

Resolved in Pega Version 7.1.9

After migrating, the processing of the deferredlist while performing an updatestatus operation generated an exception from pzMapCases. This was caused by a class mapping issue where the new classes (InsertRuleSummary, UpdateRuleSummary, DeleteRuleSummary) added in DeferredOperationsImpl did not have interfaces in DeferredOperation. This has been corrected.

SR-A1139 · Issue 204433

Ensured threshold checkbox honored in Report Wizard

Resolved in Pega Version 7.1.9

Validation errors were being generated in the custom report wizard when 'threshold' was not selected. This was an issue where the validations were being added without checking the value of the checkbox, and has been corrected.

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