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.

SR-132637 · Issue 203591

Added path checking to FirstLogCreationTime.log

Resolved in Pega Version 7.1.9

FirstLogCreationTime.log was being written to a temp folder using hard-coded logic to use a relative path within the install directory. This caused errors if the installer was trying to write the logs in an absolute path. FirstLogCreationTime.log should be written to the same directory as the rest of the logs, and this issue has been fixed by adding a condition in LogDeleteUtil.getLogCreationTimeFile() method to check for absolute paths.

SR-133747 · Issue 203813

Corrected hashtag handling for Oracle SQL generation

Resolved in Pega Version 7.1.9

Given a column name with a hashtag in an Oracle environment, the system was compiling SQL statements which caused ORA-00904 errors due to replacing the # in one variable name with an _ but leaving it as a # in another. This has been corrected.

SR-133057 · Issue 205124

System updated to better handle multi-node rule resolution

Resolved in Pega Version 7.1.9

In an upgraded multi-node environment, the error 'com.pega.pegarules.pub.database.MultipleRuleVersionException: Rule resolution identified 2 versions of the rule' was sporadically appearing. Once the issue occurred, it would persist and the only way to resolve it was to bounce the server. This was an issue with an instance of one rule being found in one node and not found in other node, and was related to the trigger logic. This should not occur with the current Pega7 version, as trigger logic has been moved into the engine and there is no longer a database trigger to fix. In order to ensure continued smooth trigger resolution, tests have been added that will check for this condition in the updates cache table to ensure that this scenario does not occur again

SR-A1479 · Issue 205900

UpgradeDataSchema target sets resume.action correctly

Resolved in Pega Version 7.1.9

Attempting to resume an upgrade after correcting a local error failed due to resume.properties having the default resume.action=install instead of =upgrade, causing the system to attempt to create tables in the data schema which already existed. The default of "install" that is set for resume mode has been removed, and the install process will now specifically set it when appropriate. A check has also been added to ensure the flag is set properly for the work being done.

SR-A1479 · Issue 205896

UpgradeDataSchema target sets resume.action correctly

Resolved in Pega Version 7.1.9

Attempting to resume an upgrade after correcting a local error failed due to resume.properties having the default resume.action=install instead of =upgrade, causing the system to attempt to create tables in the data schema which already existed. The default of "install" that is set for resume mode has been removed, and the install process will now specifically set it when appropriate. A check has also been added to ensure the flag is set properly for the work being done.

SR-A1479 · Issue 205895

UpgradeDataSchema target sets resume.action correctly

Resolved in Pega Version 7.1.9

Attempting to resume an upgrade after correcting a local error failed due to resume.properties having the default resume.action=install instead of =upgrade, causing the system to attempt to create tables in the data schema which already existed. The default of "install" that is set for resume mode has been removed, and the install process will now specifically set it when appropriate. A check has also been added to ensure the flag is set properly for the work being done.

SR-A3062 · Issue 209372

Added Unicode character error handling for JAR Import Wizard

Resolved in Pega Version 7.1.9

When there are files with Unicode characters in the import directory of a Unix system, the JAR import wizard would throw an exception and not display any files. This exception has been corrected by adding error handling in the selectfile control.

SR-A3697 · Issue 210718

Resolved Revalidate and Save freeze

Resolved in Pega Version 7.1.9

After upgrade, running revalidate and save on imported rules with the option "During Update Move To?" enabled, the first rule was processed but the process then stopped and generated the error "Uncaught TypeError: parentRow.all is not a function" if the Google Chrome or Mozilla browser is used. This problem was caused by old non-auto-generated controls, and has been resolved by modifying the ShowBulkUpdateList html section.

SR-A438 · Issue 210728

Global Resource Settings syntax examples documentation updated

Resolved in Pega Version 7.1.9

An error was found in the documentation examples for using the Global Resource Settings; this has been updated to remove the dot in the syntax examples.

SR-A789 · Issue 205761

Enhancement added for handling DB2 BLOB sizes

Resolved in Pega Version 7.1.9

BLOB schema changes were not being picked up during import due to the schema import/export process being limited in its ability to preserve the BLOB size changes being dynamically set in the db. An enhancement has been added to make meaningful use of reported blob sizes (DB2 LUW and DB2 z/OS).

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