Empty properties are not included in snapshot
Valid from Pega Version 7.2.2
History records are smaller and more efficient, because empty properties are no longer included in the snapshot. However, as a result, the history snapshot for sections might present a distorted view of the section.
prpcUtils script fails when the connection property file location is specified
Valid from Pega Version 7.2.2
If you run the --connPropFile
argument to specify the location of the connection properties file, the script fails with the following error:
Problem: failed to create task or type ac:/antcontrib.org:for
This error does not appear if you do not pass the --connPropFile
argument, or if you use the scripts.
As a workaround, edit the
file:- Open .
-
Locate the following line:
<taskdef resource="net/sf/antcontrib/antcontrib.properties" uri="ac:/antcontrib.org">
-
Replace that line with the following line.
<taskdef resource="net/sf/antcontrib/antlib.xml" uri="ac:/antcontrib.org">
-
Save and close the file.
Data schema requires update after multitenant upgrade
Valid from Pega Version 7.2.2
After an out-of-place, multitenant upgrade to Pega 7.2.2 from Pega 7.2 or later, the PR_DATA_TAG_RELEVANTRECORD table that is in the existing data schema is not present in the new rules schema. The table must be present in the rules schema for the upgrade to the rules schema to work. Copy the PR_DATA_TAG_RELEVANTRECORD table from the existing data schema to the new rules schema, and then upgrade the new rules schema. The PR_DATA_TAG_RELEVANTRECORD table is not required to be in the rules schema. After the rules schema upgrade is finished, drop the copy of the table that is in the new rules schema before you upgrade the data schema.
Push notifications and Oracle WebLogic Server 10.3.6
Valid from Pega Version 7.2.2
Pega® Platform push notifications can use WebSockets and long polling. However, for WebLogic Server 10.3.6, the push notifications feature does not work. To disable the feature, contact Pegasystems Global Customer Support.
Load balancing: HTTPD does not support WebSockets by default
Valid from Pega Version 7.2.2
If you use a load balancer with HTTPD (Hypertext Transfer Protocol Daemon), HTTPD does not support fully functional WebSockets and sticky sessions. By default, HTTPD does not support sticky sessions, because if it did, after a session was started, the same server would serve all requests for that session.