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-126448 · Issue 189959

Special character handling added to 'pzupgraderulemessages'

Resolved in Pega Version 7.1.8

The 'pzupgraderulemessages' activity was introduced to recalculate the pzinskeys of Rule-Message instances. These instances were migrated to a new table and the property, and pyclass name was made part of the key. Running this activity was made mandatory as part of upgrade/update process effective v 7.1.7. This activity selects each rule-message instance using its pzinskey and checks if it needs to be recalculated. To fetch the Rule-Message record, a plain SQL is used which did not escape any special characters in the pzinskey (\t, etc.).However, this lack of character escape was problematic for some customers who had existing rules utilizing special characters, so the activity has been updated to use a prepared statement which takes care of escaping characters in place of the generated plain SQL.

SR-126530 · Issue 188522

Enhanced error handling for exceptions generated by import

Resolved in Pega Version 7.1.8

After upgrading to a single schema on Oracle 11.2 database, the system started up showed the login page, but once logged in a blank Screen/UI would be displayed and errors were logged indicating "Failed to resolve rule file". The rule file varies depending on the content source. This issue was caused by exceptions not being handled properly by import, and has been resolved by modifying the runWithRequester method (importImpl.java) to check for Exception as a return object object from the method invocation, and propagating the exception if one is returned.

SR-126530 · Issue 193829

Enhanced error handling for exceptions generated by import

Resolved in Pega Version 7.1.8

After upgrading to a single schema on Oracle 11.2 database, the system started up showed the login page, but once logged in a blank Screen/UI would be displayed and errors were logged indicating "Failed to resolve rule file". The rule file varies depending on the content source. This issue was caused by exceptions not being handled properly by import, and has been resolved by modifying the runWithRequester method (importImpl.java) to check for Exception as a return object object from the method invocation, and propagating the exception if one is returned.

SR-126901 · Issue 190595

Handling added for temp install directory names with spaces

Resolved in Pega Version 7.1.8

If the install directory name contained spaces, the install failed at the point where the directory was used as a script parameter due to the parsing handling the name up to the space as one parameter and after the space as another parameter. In order to resolve this, handling has been added to allow temp directory names with spaces.

SR-126901 · Issue 190603

Handling added for temp install directory names with spaces

Resolved in Pega Version 7.1.8

If the install directory name contained spaces, the install failed at the point where the directory was used as a script parameter due to the parsing handling the name up to the space as one parameter and after the space as another parameter. In order to resolve this, handling has been added to allow temp directory names with spaces.

SR-127210 · Issue 190272

Added table-based cataloging

Resolved in Pega Version 7.1.8

The Update Manager catalog has been updated to reside in the Pega database instead of in the file system. This will facilitate cataloging in a multi-node environment, allow for reporting and other visibility into the catalog itself, and improve performance of dependency checking.

SR-127319 · Issue 197788

Updated cache searching for Obj-Browse on a class mapped to external table

Resolved in Pega Version 7.1.8

Unnecessary queries were being fired while using Obj-Browse on a class mapped to external table. This was caused by a class mapped to an external table and using Obj-Browse on that class fired queries to the metadata to get the columns instead of searching in the caches. The system has been updated so that the caches are read instead of firing querying the metadata every time to get the list of columns.

SR-127380 · Issue 192186

Resolved problem importing work objects into tenant layer

Resolved in Pega Version 7.1.8

Trying to import a RAP containing several work objects into the tenant layer of a multitenant system generated errors including "Import cannot proceed due to conflicting rule instances." This was caused by certain import restrictions regarding work objects belonging to a shared content class that were set during the initial development of multitenancy which are no longer required; these have now been removed.

SR-127803 · Issue 192265

Error information enhanced for Connector wizard working with external Teradata DB

Resolved in Pega Version 7.1.8

When using Teradata as an external DB, an exception was generated while using the SQL connector wizard and no rules were generated. This was caused by passing a date column that was not supported. The error has been addressed to make it more informative, but at this time the classes and properties for the fields and the mapping of the classes to the associated tables must be done manually. If the decision is made to use Date/Time properties that are mapped to Date fields, there may be time zone conversion issues. Further, mapping a Date property to the DATE column will allow the field to come across from a report definition but will not work as part of the filter (e.g. EFFT_DATE > "2014-12-01").

SR-128178 · Issue 192632

DataOnly upgrade modified to handle pr_data_products tables

Resolved in Pega Version 7.1.8

Running the upgrade.bat dataOnly true to upgrade the data schema failed while trying to insert values into the pr_data_products table. Promoting upgraded rules schema to higher environments and then upgrading the data schema is a supported upgrade procedure, but the dataOnly upgrade did not take this into account. The system has been updated such that when migrating post upgrade, it will not migrate pr_data_restore and pr_data_products tables and will fail if there are uncommitted hotfixes.

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