SR-A96149 · Issue 262711
Forced logging type changed to avoid incorrect alerts from WebLogic
Resolved in Pega Version 7.2.2
When using PRPC with WebLogic, server restarts were generating the notice that Emergency messages were present in the Server console log file. This was due to WebLogic treating logs with level greater than 1000 as emergency while PRPC was using level greater than 1000 for forced logs (infoForced and warnForced) to ensure that forced logs were not skipped in any log level setting except for level OFF. As WebLogic does not have any equivalent for forced logging, it interpreted this as an emergency. This behavioral conflict has been resolved by changing the PRPC logs from infoForced to info.
SR-A87928 · Issue 255640
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.
SR-A98244 · Issue 266698
Extract rules updated to handle BIX changes
Resolved in Pega Version 7.2.2
After upgrade, BIX was not extracting work objects with multiple child cases. Work objects without child objects were being picked up with no issues, and the child objects themselves were being extracted without issue as well. This was caused by a bug in a previous version of BIX which should have been doing a LIKE query only for class groups and not for individual classes which belong to a classgroup. BIX has now fixed the behavior and the application which was leveraging this bug as a feature is now only getting the instances of the class the extract was written against since the class is not a class group. Similar to other areas of the product (like List Views, Report Definitions etc.), when a rule is defined at the classgroup level, BIX will include its subclasses by using a LIKE query. But for classes which themselves are not a classgroup but belong to one, then BIX does not generate a LIKE query. Because of this changed behavior, Extract rule executions have been modified to keep the behavior consistent with other rules.
SR-B2033 · Issue 272929
Help doc corrected for Clipboard save location
Resolved in Pega Version 7.2.2
An error in the help file indicated the Save feature in the Clipboard Viewer should save to the database. In Pega 7, the Save feature in Clipboard Viewer only saves the page in memory and does not perform any database transactions, and the documentation has been updated to reflect this.
SR-A94935 · Issue 273957
Tomcat v7 and v8 each given dedicated implementation sections in the guide
Resolved in Pega Version 7.2.2
Due to differences between Tomcat 7 and Tomcat 8 in implementing JDBC resources, the Tomcat versions have been split into separate sections in the installation guide. In addition, the edits necessary for the context.xml file have been updated for clarification.
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-A97999 · Issue 264511
Decision Tree help updated to reflect deprecated property toggle
Resolved in Pega Version 7.2.2
The Decision Tree help documentation has been updated to reflect that the feature to toggle property name and label (Display Name or Display Label can be specified on the Decision Tree rule form) has been removed from the product as of v7.1.7.