SR-A92640 · Issue 266679
Upgrade rules considers DADT instances for mapping
Resolved in Pega Version 7.2.2
When migrating and upgrading the rules tables to a new schema, the _upgradeRuleBase task was trying to remap some work classes/tables to pr_other. This was due to the class name being compared with case sensitivity when the site had DADT instances for which the class name was not same as the class instance. To resolve this, the check has been made case insensitive so DADT instances are not missed.
SR-A102766 · Issue 269648
db2zOS tablespace script logic updated
Resolved in Pega Version 7.2.2
When running the generateddl script against a db2zos database, the tool determines for each table if the current tablespace page size needs to be increased before the DDL changes can be applied. For the pc_work_social table, while the tool included the size of new columns when it calculated the projected table size, it did not take into account the altering of existing columns. This has been fixed by tightening up the JDBC resource handling.
SR-A98103 · Issue 266253
Scheduled recurring Purge/Archive set to reuse specified start time
Resolved in Pega Version 7.2.2
When scheduled to run every day at a particular time, the Purge/Archive function started later each time. This was due to the function using the Agent running time for the rescheduling, starting the next day at the time it ended. The function has now been modified to use the customer-specified start time instead of calculating the Agent time.
SR-A86384 · Issue 258433
Diagnostic logging added for "No stream to display" error
Resolved in Pega Version 7.2.2
Diagnostic logging has been added to better address the "No stream to display" error on the UI. When enabled, the logger will capture the postDataBytes and corresponding postDataString that are returned.
SR-A21743 · Issue 256234
Support added for WebLogic 12.2.1
Resolved in Pega Version 7.2.2
Support has been added for WebLogic 12.2.1, which introduces a new Class Loader between the application and System Class Loader.
SR-A76628 · Issue 255871
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-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-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.