SR-A88372 · Issue 259465
BIX log now includes BIX version info
Resolved in Pega Version 7.2.2
In order to enable better system tuning, the system has been updated to specify the BIX version in use in the logs. i.e. BIX Version : 7.1.9
SR-A88308 · Issue 256840
Agent Interval setting documentation updated
Resolved in Pega Version 7.2.2
On the Agents rule form there are two separate Interval areas where you can specify how often agents should run. Previously, the help for this rule form indicated that a value of at least 5 (seconds) should be entered and that a value below 5 would generate a validation error. However, the default settings only support a value of 30 seconds or greater unless a custom setting is created. The help file has been updated to clarify this. The following is the custom setting necessary for values below 30 seconds:
SR-A94935 · Issue 273588
Installation guide updated for
Resolved in Pega Version 7.2.2
The 7.2.1 installation guides incorrectly showed the edits needed to the context.xml file. In "Configuring Tomcat by editing the context.xml file", steps 4 and 5 are incorrect and should have included the type="java.lang.String" specification (similar to steps 6 and 7). The following pages have been updated: tomcat oracle p35 tomcat db2luw p32 tomcat mssql p30 tomcat postgreSQL p33
SR-A86228 · Issue 256027
Documentation corrected for connection properties with WAS 8.5.5.7 and MSSQL 2014
Resolved in Pega Version 7.2.2
The case specified in the install guide for including the "SelectMethod" and "SendStringParameterasUnicode" connection properties was incorrect, causing poor performance in the import process when using WAS 8.5.5.7 and MSSQL 2014. The documentation has been corrected.
SR-A15627 · Issue 232738
JBoss shutdown errors resolved
Resolved in Pega Version 7.2.2
During a controlled shutdown, database-level exceptions occurred and a hard reset was required. This was traced to the container not correctly detecting dependencies, leading to JBoss prematurely terminating JMS and JDBC resources that were needed during Pega shutdown. Pega applications on JBoss now contain information to ensure the application server understands that this resource has dependent processes and the lookup-name (with the JBoss specific namespace) is maintained correctly to make sure it isn't cleaned up prematurely. The web.xml file has also been updated to include a lookup-name in the entry for ResourceRef_1 to handle cases where the datasources are injected using CLI scripts after JBoss is started and before Pega is deployed.
SR-A97991 · Issue 263957
Index reference synchronizer upgraded to capture previously shipped rulesets during upgrade
Resolved in Pega Version 7.2.2
During upgrade, some sites were seeing an SQLIntegrityConstraintViolationException error. This was caused by the presence of rulesets (e.g. PegaUVU, PredictiveAnalytics-UI) that were once shipped but are no longer, but that have rules that are still shipped. To correct this problem, the index reference synchronizer has been upgraded to capture those previously shipped rulesets.
SR-A98390 · Issue 252437
Scheduled report cleanup error resolved
Resolved in Pega Version 7.2.2
Exceptions were thrown in the logs by the scheduled reports task when trying to clean up the previous day's generated attachment reports. This was due to the name exceeding the length restriction on the property (60 characters) and failing validation, and has been fixed by truncating the field.
SR-A87928 · Issue 255259
Fixed cataloging for v5 hotfixes
Resolved in Pega Version 7.2.2
Recent modifications to obtaining catalogs for supporting additional products (i.e. frameworks) caused a regression in being able to check dependency information on v5 hotfixes, preventing DL files from being created for them. This has been fixed.
INC-140279 · Issue 597756
JMX logging added to upgrade diagnostics
Resolved in Pega Version 8.4.4
In order to improve diagnostic information, infoForced loggers have been added for debugging upgrade issues related to JMX calls to enable and disable rules creation.
INC-144555 · Issue 603071
Changelog cleanup added for de-optimized properties
Resolved in Pega Version 8.4.4
Unwanted optimization was automatically added to properties for the Application-Work-Casetype class created using the wizard in the App Studio. Attempts to remove the optimization did not work: the property advance tab was showing the optimized classes details even after deleting and recreating the property. When a property is optimized the system adds entries to pr_changelog for the list of classes it has optimized. When the property was deleted, the pr_changelog was not cleared. This was a missed usecase, and has been resolved by overriding the Cleanup activity at Rule-Obj-Property class to delete the pr_changelog entry associated with that if it is present.