Published Release Notes

Empty properties are not included in snapshot

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

If you run the prpcUtils command-line script and pass 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 prpcServiceUtils scripts.

As a workaround, edit the prpcUtilsWrapper.xml file:

1. Open <distribution>\scripts\utils\prpcUtilsWrapper.xml.

2. Locate the following line:

   <taskdef resource="net/sf/antcontrib/antcontrib.properties" uri="ac:/antcontrib.org">

3. Replace that line with the following line.

   <taskdef resource="net/sf/antcontrib/antlib.xml" uri="ac:/antcontrib.org">

4. Save and close the file.

Data schema requires update after multitenant upgrade

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.

Support for rule rebasing

You can now rebase the rules on your development server with the most recently committed rules from a centralized system of record (SOR). For example, after rules are merged on the SOR, you can rebase your development application to refresh your application with the merged rules. Development teams working in two separate development environments can share their changes, keep their local rulebases synchronized, and reduce the probability of conflicts with other development teams.

For more information, see Rule rebasing.

Push notifications and Oracle WebLogic Server 10.3.6

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

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.

Support for Apache Cassandra

The Pega^® Platform can now read data from and write data to an Apache Cassandra database. Apache Cassandra is a NoSQL database that you can use when a NoSQL database better meets your scalability and processing requirements.

For a list of supported and unsupported features, see Apache Cassandra support.

Apply logic to data import fields

When importing data from an external system, you can translate data fields into values that can be read by Pega^® Platform. From the Import wizard, you can do the following actions:

• Apply a decision tree or decision table to the data that is imported for a field.
• Use imported data for a field to look up a value in another record. For example, you can look up the key of a record that uses an external identifier to populate a foreign key field.
• Create templates that contain business logic, which eliminates the need to handle data transformations manually during preprocessing.

For more information, see Transforming data during import.

Expose properties in Decision Data Store

You can now expose properties in Cassandra-based Decision Data Store data sets. With this solution, you can update single properties in extended customer analytic records (XCAR) without having to update the full customer record.

For more information, see XCAR in Decision Data Store.

The Scratch Pad tool is no longer available

The Scratch Pad tool is no longer available. To add properties to a report from an end user portal, use the Data Explorer. The Data Explorer provides an efficient way to find a property or calculation to include as a column in a report.

For more information, see Data Explorer.