INC-209435 · Issue 707374
Column population error downgraded to warning
Resolved in Pega Version 8.8
A Column Population job run after deployment for some classes was logging the error "Class does not exist", but no property was identified and no impact to the system was seen. This error has been downgraded to a warning.
INC-210513 · Issue 710344
Added handling for clustered index on the pr4_rule table during migration
Resolved in Pega Version 8.8
When attempting to migrate the rules schema to RULES85 and temp data schema DATA85, the upgrade was becoming stuck in a loop while working to generate declarative indexes for Rule-HTML-Paragraph. Investigation showed the infinite looping happened only for classes mapped to the pr4_rule and with instance count of more than (num of threads * batch size). This was due to the presence of a clustered index on the pr4_rule table causing the resultset to return an infinite number of records in SQLServer, and has been resolved with an update to leverage the total record count to iterate the resultset instead of depending on the resultset.next().
INC-211299 · Issue 706316
Handling updated for rule export errors
Resolved in Pega Version 8.8
After exporting the rules from E2E, the import to the production mirror failed. Investigation showed that the process encountered a time out from an Adaptive Decision Manager table when exporting the product rule, resulting in the product file not containing the mandatory jar files. This has been resolved by updating the handling of errors during export, and suppressing auto-chaining when generating app JSON.
INC-215877 · Issue 715234
Handling added for Oracle "NUMERIC" type
Resolved in Pega Version 8.8
When a product rule was created in an environment using Oracle, importing the product into the cloud environment with database table schema changes resulted in errors. This was traced to a change in Oracle's JDBC driver which was reporting Number as a JDBC "NUMERIC" type instead of the previous "DECIMAL". Pega uses the NUMBER data type and expected a type=DECIMAL for an Oracle number, causing the errors. This has been resolved by adding a check for flex numbers if column is NUMERIC.
INC-217855 · Issue 731911
Uncommitted hotfix able to Rollback All after install
Resolved in Pega Version 8.8
A security hotfix was installed through Hotfix manager and left as uncommitted. When new hotfixes for the same files were received, the process required the uncommitted hotfixes to be rolled back, but attempting to do so generated exceptions in the logs reading "Exception in rolling back the archive PegaRULES Process Commander: code: 0 SQLState: Message: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (PRPC_RULE_ADM_P7.PR_ENGINECLASSES_PK) violated". The issue was caused by the Date field only accepting dd/mm/yyyy HH:MI:SS, so attempting to insert two records of the same jar in the pr_engineclass generated this error from pr_data_restore in Oracle. To resolve this, an update has been made to insert rolled-back jar removals with their original patch date to avoid PK conflicts.
INC-222835 · Issue 721065
UI messages updated for hotfix catalog issues
Resolved in Pega Version 8.8
Here is the issue/enhancement request that was seen and can be a more general issue. After the restart there is not a catalog available and for environments that cannot access the internet this means they cannot actually do anything like commit all or rollback all. When clients tried this they clicked on the button and nothing happened. If you look in the PegaRules log you see a message that tells you that the catalog is not available.
INC-223074 · Issue 720454
Fallback handling improved for import synchronization
Resolved in Pega Version 8.8
Upgrade to CRM 8.7 was failing during the import of the CRM jar. There are some rare edge cases where instances may be in the database, but not visible to the engine until the import is already underway, such as when rollback has deleted a class definition and mapping but not the instances of the class itself. To mitigate the risk of PK constraint violations when this happens, the process has been modified to mark all the instances that cannot be directly synchronized as updates so that the data layer will upsert them.
INC-229641 · Issue 739454
Enhanced logging related to rule skimming
Resolved in Pega Version 8.8
In order to assist with diagnosing issues related to skimming of a ruleset, an update has been made which will log the complete stack trace along with the pzinskey being processed in debug mode.
INC-RCA-921 · Issue 713987
Updated debug logging
Resolved in Pega Version 8.8
Debug logging within IndexReferenceSynchronizer and FastLoader has been updated. With this update, IndexReferenceSynchronizer debug logging will indicate what the action is for each instance, FastLoader will include information about the keys being loaded and statements being executed, and duplicate logging has been removed from BatchSQLExecutors.
INC-192935 · Issue 688463
Added deferred loading for email cases
Resolved in Pega Version 8.8
When there were a significant number of email interactions on an email case, delays were seen when loading the case in the UI. Investigation traced this to a high number of database calls along with the BLOBs also being open. To improve performance, the new rule pyDeferLoadEmails has been added which toggles the UI and loads emails faster. In addition, the button label has been modified to read "View all emails" in place of "Show all" while defer load is enabled.