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.

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.

Internal rules in search results and explorers

Using old: is no longer supported in search. You can include internal rules in search results and make them available in the Application and Records explorers. Include internal rules in search results either by adding the PegaDevelopmentruleset to your application or by clicking the Enable diagnostic features option in your operator preferences.

Ability to include all properties in search results

You can now include all properties in a class in search results so that they can be used in report filtering. When the Enable search results for all properties option is selected on the Custom Search Properties rule form, all top level and embedded page scalar properties for the class are indexed and returned in search results, and all embedded page list, page group, value list, and value group properties for the class are indexed but not returned in search results. Selecting this option might affect performance.

In addition, by default, properties defined in the Data-Tag-RelevantRecord instance for a class are indexed and returned in search results and do not need to be explicitly configured.

You must reindex search after selecting or clearing Enable search results for all properties and after changing the properties that are defined in the Data-Tag-RelevantRecord instance.

For more information, see Specifying custom search properties.

SAML single sign-on is easier to configure

Implementing SAML single sign-on (SSO) login authentication in your application is now less complex. You can now configure most requirements that used custom activities or Java code in previous releases from the Authentication services form.

For more information, see Creating an authentication service.

Support for controlling binary file upload in Pega Mobile Client

The Client Store API of Pega^® Mobile Client has been modified so that you can suspend and resume the process of uploading binary files to the server. You can also check the state of the file uploading process. As a result, custom mobile app users can process their work items without having to wait for the synchronization process to finish.

For more information, see Pega Mobile Client API methods for controlling binary data upload and Client Store API.

Support for large binary data item storage in Pega Mobile Client and offline case attachments in Pega Platform

Pega^® Mobile Client can now store and synchronize large binary data items and their corresponding actions from the action queue on Android and iOS devices. As a result, custom mobile app users can view, attach, and delete data files, whether the device is online or offline. For this function to work, you must enable offline case attachment support, which allows your custom mobile apps to synchronize case attachments between the Pega Platform and the mobile device.

For more information, see Enabling offline case attachments support and Client Store API.