SR-A22672 · Issue 243213
Use Pega Log Analyzer in place of Alerts.xls Excel Template
Resolved in Pega Version 7.2.1
A documentation error incorrectly referred to the Alerts.xls Excel template as being available on the PDN. That file is no longer available, and the Pega Log Analyzer should be used instead: https://pdn.pega.com/community/pega-exchange/pegarules-log-analyzer
SR-A23134 · Issue 243870
Resolved upgrade exception caused by non-standard requestor setting
Resolved in Pega Version 7.2.1
Upgrading to v7.2 was failing if the 'Requestor Types' (DATA-ADMIN-REQUESTOR instances) ACCESS GROUPs had been modified in the previous version for the System Name 'prpc'. This modification caused the PRPC requestors to not be replaced during upgrade. To address this issue, the installation will create a RAP to import into the SDE that will check for this condition, and the PRPC Requestors have been updated such that they cannot be modified. See also: Process Commander V6 help "About Requestor Type data instances" and "When and how to change a system name" for more background information about Requestor Types.
SR-A23339 · Issue 247921
Non-versioned class rule forms updated during upgrade
Resolved in Pega Version 7.2.1
The non-versioned class rules in an environment were skipped during upgrade due to an error in the RevalidateAndSave function. This has been corrected.
SR-A23979 · Issue 246353
Revamped help docs to clarify ServiceExport directory config
Resolved in Pega Version 7.2.1
An error in the help documentation did not correctly outline the method for changing the ServiceExport directory by modifying prconfig.xml. The directory location is hard coded to StaticContent/global/ServiceExport in the temporary directory, but the location of the temporary directory is configurable using the Initialization/explicitTempDir setting. Changes have been made to the help files to clarify this.
SR-A24052 · Issue 248427
Orphaned work objects purged by class
Resolved in Pega Version 7.2.1
Orphaned work objects were not purged when their parent was deleted from the database. To resolve this, selecting a Work- object class for purging will also purge all of the orphans in that class.
SR-A24478 · Issue 247983
Diagnostic logging added to upgrade Java Syntax task
Resolved in Pega Version 7.2.1
While running the upgrade.sh script to upgrade an in-place single-schema upgrade, the script halted while performing "Scanning Class" operations and remained there for over 8 hours. Attempting to resume appeared to proceed for a few minutes before halting again and remaining at the same point. The problem was traced to list views getting the PMD going into an infinite loop during the upgrade java syntax task. Diagnostic logging has been added to the PreUpgradeRuleAnalyzer/JavaParser code to add a log statement to print any keys which are getting processed when errors occur.
SR-A24517 · Issue 246951
JMX Javadoc available for download
Resolved in Pega Version 7.2.1
The document MBeanJMXJavadoc.zip was last shipped in Pega 7.1.7 and was not present in the on-line documentation. The Mbean Javadoc package is now available for download at the following link: https://pdn.pega.com/release-note/mbean-javadocs-download-file
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.
INC-163791 · Issue 704028
Simplified default reference time calculations
Resolved in Pega Version 8.6.4
After a job scheduler was configured to run at Start time = 21:00:00 for Time zone = Europe/London, the scheduler determined 20:00:00 as the next start time. This was due to the calculation for the next start time using the time zone offset calculation pattern for the date and time stored in System-Runtime-Context.pxCreateDateTime, which had difficulty with changes to the time zone definition implemented in the time between the given date and today (meaning the current time) such as daylight savings time. To resolve this, the default reference time from System Runtime Context will be 'now' instead of Date(0).