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-D24900 · Issue 503873
Security update for RequestMap error logging
Resolved in Pega Version 8.3.1
In HttpAPI, the RequestMap contains Cookie information. In error conditions, this map gets logged. An update has been made to ensure that the Cookie value is not logged if there is an error.
SR-D27644 · Issue 497611
Uploaded attachments will receive a unique name to prevent overwriting
Resolved in Pega Version 8.3.1
An issue with an incorrect file being attached to a work object was traced to overlapping processes. When files are uploaded, they are first saved to common HDD directory and then read into memory and deleted from the HDD area. Files will overwrite other file carrying the same name, which is a problem if the first file is not completely uploaded and is waiting in the common directory and some other file with the same name is uploaded on top of it. To resolve this, an update has been made to ensure file names are appended with a unique identifier to distinguish between files carrying the same names and keep them from overwriting each other.
SR-D28184 · Issue 497165
Verbose debug logging removed from LockUtils
Resolved in Pega Version 8.3.1
Verbose debug logging that had been added to the "LockUtils" class to print when the lock was acquired or released and include the associated stacktrace has now been removed as it interfered with diagnosing locking issues when threads were getting blocked.