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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-160382 · Issue 630714

Added handling for double quotes when converting tables

Resolved in Pega Version 8.6

After importing some packages from development to production, DDL conversion failed for tables with 30 characters in the table name when the import file contained a "Create VIEW" sentence. This was due to the addition of double quotes (" "). The table rename utility was not expecting to handle quoted table names, so as a result the addition of the quotation mark characters were included in the length calculation, and when renaming was performed it yielded syntactically invalid names (with leading " in the name). To resolve this, an update has been made which will strip quotes from table names being passed into TableRenameUtil.

INC-162360 · Issue 635817

Unneeded AUC error percentage calculation removed for better system performance

Resolved in Pega Version 8.6

When generating snapshots of the ADM models, an inefficiency in the metric calculation for the AUC error percentage caused an excessive amount of memory to be allocated which could cause slowdown or require a system reboot. This has been resolved by removing the problematic AUC error percentage calculation as it is not used in the UI.

INC-163940 · Issue 634491

CustomerData schema added to list of databases for optimization

Resolved in Pega Version 8.6

was no "Create?" column. This column appeared for the PegaDATA database but not for CustomerData. To resolve this, the Optimize Schema Landing Page has been updated to treat the CustomerData schema as a shipped Pega database.

INC-174321 · Issue 664240

SSLContext created using protocol from REST connector rule form

Resolved in Pega Version 8.4.6

After upgrading to IBM websphere v9.0.5.6 or higher, API calls Like REST, Connect-HTTP etc were failing to connect to endpoints using TLSv1.2. Investigation showed that although the connector was configured to send TLSv1.2, the ClientHello handshake was triggered for TLSv1.3. Because the SSLContext was created with highest version supported by protocol in the WAS container, this has been resolved by modifying the code to create SSLContext based on the the protocol selected in the REST connector rule form. Additionally, please note that the Connect-HTTP connector has been deprecated and the Connect-REST capabilities in the platform should be used instead.

INC-184756 · Issue 667323

Static assembler correctly creates temp directory

Resolved in Pega Version 8.4.6

Static Assembly CLI was failing while creating a temp directory. This was traced to an issue with staticAssembler.xml, and has been resolved. In addition, security improvements have been added to the XML transformer.

INC-190722 · Issue 676403

Ruleset Restoration Utility repaired

Resolved in Pega Version 8.4.6

Attempting to use the standard Ruleset Restoration utility after update was resulting in a "Status:fail Operator:Unauthenticated or not available Node:No ID available" error message. This was a missed use case for the refactoring done around importing rules, and was caused by the utility calling the deprecated Importable.isValidImport() method. This has been resolved by updating the import activity to restore its functionality.

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