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-A18998 · Issue 236896

Document updated for WAS JNDI dataSourceAdmin binding identifiers

Resolved in Pega Version 7.2.1

Page 80 of the Pega 7.2 Platform Upgrade Guide describes the procedure to create the JNDI binding identifiers for dual-user configuration. In that description, the String value for the following identifiers is not correct. prconfig/database/databases/PegaDATA/dataSourceAdmin prconfig/database/databases/PegaRULES/dataSourceAdmin The string value should be the "the JNDI name of the Admin data source for the data/rule schema" instead of "the schema name of your data/rules schema" The same issue is present in the Pega 7 Platform Installation Guides for WebSphere, and both documentation areas have been updated.

SR-A19814 · Issue 237605

Entropy pool explicitly coded for UNIX/Linux Oracle installations

Resolved in Pega Version 7.2.1

When running a new install on an Oracle database in a UNIX environment, install was failing repeatedly at the same point when attempting to import one of the application bundle components. This issue was traced to the way the newer versions of the Oracle JDBC driver gather entropy by defaulting to the use of /dev/random. When running in an environment where there this is not a lot of noise, the entropy pool will eventually be empty and the connection will be reset. Earlier versions of the Oracle JDBC driver did not see this issue. To resolve this, in the event that a deployment is being performed on a UNIX/Linux platform using an Oracle database, the -Djava.security.egd=file:///dev/urandom will be specified whenever a java utility is started.

SR-A19865 · Issue 240029

Migration script checks for compressed data before inflating

Resolved in Pega Version 7.2.1

While upgrading, the migrate script was failing while trying to create the tables.txt file content. This was traced to data handling. During engine start-up, a check is performed to determine whether bytes are compressed or not, and inflate those that are compressed so they can be read. The migration utility did not have this check, and by default went ahead and inflated. This caused exceptions when encountering BLOBs, as a BLOB contains both CompressedBytes and UnCompressedBytes. A check has now been added to the migration script so inflation is only done as needed.

SR-A20593 · Issue 238898

Pagination added to Hotfix Manager

Resolved in Pega Version 7.2.1

If there were more than 10 uncommitted hotfixes, the Hotfix Manager was not able to display them all due to a page limit and pagination being disabled by default. The pagination footer has now been made visible to allow viewing of the full list of uncommitted fixes.

SR-A21196 · Issue 233151

RAP data pages made consistent across environments

Resolved in Pega Version 7.2.1

It was found that the Data pages for a RAP (rule-admin-product) deployed from dev1 to dev2 differed from the results of the same RAP deployed to demo if it contained a PageList(P1) inside which there is a PageList(P2) property that refers to Data Page (list type). This was caused by a handling difference between the two environments, and checks have been added to ensure consistent results.

SR-A21487 · Issue 241066

Corrected GRANT generation for DB2 users

Resolved in Pega Version 7.2.1

When importing a RAP with a view into a DB2 10.1 LUW database, the GRANT statements were failing because of invalid syntax and the view creation was not executed. This was caused by the user name not being properly appended to the grant statement generation for DB2 users, and has been fixed.

SR-A21613 · Issue 241399

Upgrade order modified for in-place schema migration

Resolved in Pega Version 7.2.1

An in-place update of a split-schema was generating SQL exceptions. Two issues were found: For the pr_index_circumstance_def table there was a bit column type which was not anticipated, and as a result the constraints/indexes were not detected as being already installed and the application of the generated DDL failed when it tried to create them. The secondary issue was that the DDL generated by the update script was sorted so that all of the drops happened first, causing a situation where the pr_page_store_PK was trying to be dropped at a point where it did not exist. The resolution is to issue all drops first to avoid the dependency issue, then let the Schema Manager determine order so it performs the rule schema updates first and then performs the data schema updates during in-place upgrades.

SR-A21741 · Issue 248725

Fixed drilldowns and filtering with encrypted property

Resolved in Pega Version 7.2.1

After encryption of a property, filtering and drill down reports stopped working. "TAB" space is added as first character along with encryption data to store a textencrypt property type in the database, but while performing the drill down the TAB key is not appended. Instead "/t" character is added which does not fetch the results. To fix this, the JavaScript has been modified to ensure "\t" isn't added so drill down activity will get the proper results.

SR-A22147 · Issue 244096

Autogenerated prconfig sets v6 or v7 based on detection

Resolved in Pega Version 7.2.1

The autogenerated prpcUtils prconfig.xml file was setting the database/storageVersion to 6. In order to facilitate other setups, a flag has been provided in prpcUtils.properties as pega.storageVersion which will set the value in generated prconfig.xml to an empty string so the engine handles setting this to 6 or 7 in the same way that is possible when running the system.

SR-A22263 · Issue 242102

Improved error reporting for PE install

Resolved in Pega Version 7.2.1

In order to facilitate debugging, attempting to install Pega Express from a directory with a space in the name will generate an error on the screen reiterating the installation instructions requiring that the directory name not contain a space.

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