SR-A9198 · Issue 218533
Text retrieval for deprecated "Query" button updated for universal browser support
Resolved in Pega Version 7.2
The Firefox popup window provided by the Product rule when querying "Individual Instances to Include" failed to transpose the selected rule information back into the Product ruleform when the OK button was clicked. This was due to the use of the deprecated "Query" button, which does not have support for all browsers, to launch the ListView. To handle this, the node text retrieval method in DataInstancesQueryScript has been updated to use the 'textContent' function (compatible with all browsers) instead of the previous 'innerText'.
SR-A10839 · Issue 222017
Added handling for null rollback info in hotfix autocommit
Resolved in Pega Version 7.2
If AutoCommit was selected while installing a hotfix, the auto-commit would fail and leave the hotfix in an Uncommitted state if there were dependent hotfixes where changes were covered by the parent and the child was superseded after installing the parent. Manual commitment of the hotfix worked as expected. This was an edge case where the older hotfix did not get rollback information saved since its components were already installed or superseded, and AutoCommit has been updated to handle this missing information.
SR-A10327 · Issue 222830
Upgrade Assistant enhanced to better resume interrupted process
Resolved in Pega Version 7.2
If the system suffered a crash during upgrade, IUA was incorrectly identifying the DB as having completed the upgrade and would import outstanding rules based on the perceived Database BLOB version. This led to a storage-type mismatch between Prod and all lower environments, and BIX jobs would fail due to not being upgraded. An enhancement has been added to the Upgrade Assistant to correctly resume an interrupted upgrade process.
SR-A12287 · Issue 223279
Alter Script generates correct SQL for Oracle db
Resolved in Pega Version 7.2
During installation, an incorrect Alter Script was being generated while importing the JAR file due to a missing check on the 'required' XML attribute for dbtype Oracle to decide whether it should be null or not null. This has been corrected to honor the 'required' attribute and accordingly the generated SQL will be appended with null/not null string.
SR-A12687 · Issue 226506
Skimming logic corrected
Resolved in Pega Version 7.2
The skimming logic (PegaRULESMove_Skimming_Query) has been updated to correctly repopulate the query page in order to return a more accurate rules count.
SR-A2733 · Issue 220049
Migration process handles underlying varchar CHAR
Resolved in Pega Version 7.2
Handling for CHAR length semantics has been added for imports of rule schema to support Oracle varchar2 columns, and the import/export will correctly deal with the circumstanced columns of CASETYPEVERSION and PXREFOBJECTCLASS.
INC-167311 · Issue 646477
Updated upgrade handling for migrating work objects
Resolved in Pega Version 8.3.6
After upgrading from Pega 6.2 to 8.3, the work migrated work objects were missing SLAs due to missed entries in the assignment tables (PC_ASSIGN_WORKLIST/ PC_ASSIGN_WORKBASKET) . The SLA was firing, but the processing failed due to the fact the runtime could not resolve a 'AddHistoryPage' library function. In this case, multiple upgrades of the application dating back to Pega 4 resulted in the runtime context containing older ruleset versions in higher ruleset versions, hiding the underlying Pega 8 version of the rule. For releases prior to Pega 7.3, Rule-Application was stored in pr4_rule and will be migrated to pr4_rule_application during upgrades. However, since Context Upgrade is run before Optimize Newly Exposed Columns, the pyDependsOnName won't always be populated. To resolve this, the system will filter based on the value in the blob rather than the exposed column so there will be a value regardless of the upgrade-from version.
INC-172675 · Issue 649451
Configuration added for extending queue processor timeout
Resolved in Pega Version 8.3.6
Alerts for queue processor (QP) items which took more than 15 minutes to run could result in the system marking the node as 'unhealthy'. In environments with Pega Health Check enabled, this would shut down the node gracefully. It was not possible to change this default as it was hardcoded. In order to support systems that may have custom processes that run beyond 15 minutes, a a new setting has been exposed that allows configuration of the interval after which a node with long-running queue processor is marked as unhealthy and is restarted. By default this remains 900000 milliseconds / 900 seconds / 15 minutes, but it may be adjusted up to 24 hours to avoid premature node shutdown. The stale thread detection mechanism will take that setting into account and use the provided value or default to 15 minutes if the value was not provided. In addition, the threshold's units in the UI have been changed from ms to seconds.