SR-128285 · Issue 193082
Added handling for column size mismatch on Oracle import
Resolved in Pega Version 7.1.8
When upgrading versions of CMF, errors were generated when importing the Pega jar file. The exported schema has pyAccessibility and pyBrowserSupportLevel datatypes as "integer" with size 10, but on the target Oracle database the same column was defined as Number with default precision and scale (0, -127). While importing, the logic checks for column compatibility and was generating an alter statement based on this scale mismatch. This has been resolved by modifying the system to detect that the metadata is returning the new style of NUMBER column metadata handling it correctly.
SR-128475 · Issue 194266
DB Trigger logic refactored for better vw table syncing
Resolved in Pega Version 7.1.8
There are many times in customer environments where for whatever reason the database triggers are disabled for a period of time and thus the vw table gets out of sync. Typically in that case the triggers are reenabled and a statement like "update pr4_rule_file set pzinskey=pzinskey" is run to get the vw table populated correctly. However, if the system was being upgraded the statement would update an existing row in the vw table but it would not add any missing rows to the vw table during migration. To ensure that all rows are handled correctly, trigger logic has been completely refactored for 7.1.8.
SR-128932 · Issue 194789
Added support for -x and -y parameters to ApplicationBundle import
Resolved in Pega Version 7.1.8
Previously, the use of the -x and -y parameters in the command line utility prpcUtils only worked with PegaArchives and not ApplicationBundle archives. In order to facilitate automation, the app bundle command line import command now honors the -x (override) and -y (skip) import parameters, and these options will be passed along to any nested par files.
SR-131199 · Issue 201548
Smoothed editing of data tables mapped to external DB
Resolved in Pega Version 7.1.8
It was not possible to edit a data table mapped to an external database table with column name different from that of the property. To resolve this, the system will ensure that the external mappings take precedence while trying to update the data table.
SR-131266 · Issue 199637
Cleared exception during import of RAP by prpcUtils
Resolved in Pega Version 7.1.8
When attempting to import a RAP file through command line by using prpcUtils.sh, the build was successful and all the rules were imported but an SQL exception was generated related to the execution of Stored Procedure. The RAP file did not contain any code to execute stored procedure, so the execution was found to have been done internally by prpcUtils.sh. To prevent this, prpcUtils has been updated to use the data schema as the default schema for the connection while running against either of the DB2 dbs.
SR-131347 · Issue 198661
Changed Dependency Checker table-based cataloging to be case insensitive
Resolved in Pega Version 7.1.8
After updating, the Dependency Checker and Packager functions for v5 items in the table-base catalog features were not finding existing cataloged items that contained mixed case IDs. To resolve this, the dependency checking code has been modified to be case insensitive.
SR-132265 · Issue 200632
Improved hotfix detection
Resolved in Pega Version 7.1.8
Migrating from ML6 to ML7 was failing with an error reporting the system contained hotfixes that were generated after the release of ML7. This was due to the ML Readiness step incorrectly identifying pre-7.1 rules as having been updated after the upgrade to 7.1.6. This happened when the revalidate and save was run after the release of ML7, which updated the pxUpdateDateTime for the rules in question and led to them being caught by the validation. This was meant to catch hotfixes, and the handling has been improved to avoid this error.
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