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-C79731 · Issue 417958

TestID remains unique in grids

Resolved in Pega Version 8.1.3

To support automated testing, testID will maintain unique IDs for grid rows and RDL rows.

SR-C79762 · Issue 419158

Decision table decision shape produces correct connector

Resolved in Pega Version 8.1.3

After adding a decision shape and making its type "Decision Table", the connector that was automatically built showed the condition type as "Result", but incorrectly labeled it as a When rule. This was traced to a missed use case in the decision related connectors, and has been corrected.

SR-C79941 · Issue 416722

Corrected JSON for eventType DisableOperators in the security event log

Resolved in Pega Version 8.1.3

An event entry in PegaRULES-SecurityEvent.log was generating invalid JSON. This was traced to eventType DisableOperators (not disable operators) containing a message attribute with unescaped double quote characters surrounding the operator names. This has been fixed.

SR-C80050 · Issue 417604

Schema name made consistent for DDL generation

Resolved in Pega Version 8.1.3

A platform upgrade failed if there were application schemas configured with a table configuration that specified a schema other than the rules schema. This was an issue caused by the generated DDL having the incorrect schema name for the table due to the name being hard-coded in the Data-Admin-DB-Table entry definition. The system was using this schema name to find the table and generate the correct changes, but the SQL statement used the table from the database connection instead of the override. When the XML that represents the difference between the "source" and "target" state is generated, the system is supposed to replace the schema name with the target schema name. However, if the source schema name is blank that step was skipped in order to defer to the connection for shipped tables. In order to ensure that the system can generate the correct DDL and complete the upgrade, the system will now always replace the schema name regardless of the source or target value.

SR-C80076 · Issue 419094

Added check before deleting pxObjClass to avoid agent runtime exceptions

Resolved in Pega Version 8.1.3

When the rule was not assembled, agents were failing with exceptions. During label control assembly execution, standard attributes for label assembly including pxObjClass are removed from the cell page. There is a catch for the exception during cell trimming for browser requests, but the customer agent was failing because UnmodifiablePropertyException is a runtime exception that sets the step status to fail. This has been fixed by adding a check when attempting to delete a property from Clipboard page: if the property is pxObjClass, it will not be deleted.

SR-C80084 · Issue 417239

Target connectivity preference updated in Revision Manager to address deployment error

Resolved in Pega Version 8.1.3

Using the deployment page to deploy a revision or migrate it to a target environment was failing. This has been resolved by correcting the target connectivity preference in the connector rules.

SR-C80215 · Issue 421850

Migrated Data Flows open correctly from the data flow landing page

Resolved in Pega Version 8.1.3

After upgrade, Data Flows made in an earlier version could not be opened from the data flow landing page. Instead, a generic error screen was displayed and an NPE on activity pxMigrate was logged. This was caused by a missing null pointer check, and has been corrected.

SR-C80958 · Issue 419200

Added check for appname to avoid HarnessFail execution error on Mashup reload

Resolved in Pega Version 8.1.3

A HarnessFail execution error was occurring on Mashup reload. This was caused by the appname being appended twice during the reload, and has been resolved by adding a check to the _finalizeNavURL method in the PegaCompositeGadgetMgr.js file to remove appName if it is present in the URL to prevent duplication.

SR-C81111 · Issue 417909

Performance improvements made for IH summary use

Resolved in Pega Version 8.1.3

Enabling IH summaries in an adaptive model or using them in a strategy was impacting performance by as much as 300 milliseconds. Improvements have now been made to streamline Cassandra node health checks, to eliminate unnecessary duplicate calls to the DB, and to stop the DSS from being read on each single case dataflow execution.

SR-C81262 · Issue 418057

Failed delete instances now correctly logged

Resolved in Pega Version 8.1.3

After configuring rule-access-when on delete instances for a data class, the failed instances were not shown in the error log file. This has been resolved by correcting the path of the error CSV file in the pzDeleteRecords activity.

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