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.

Upgrade/update fails if PostGIS is applied to PegaRULES or PegaDATA schema

If you use the PostGIS extension to a PostgreSQL database, upgrading or updating the Pega 7 Platform fails if the extension has been applied to either the PegaRULES or PegaDATA schema. PostGIS can be applied to any other schema.

Primary key constraint error when using JBoss

A primary key constraint violation exception might occur in the following situation: you use JBoss EAP 6.4 and SQL Server 2012 with a JDBC 4 driver, and you use two or more file listeners or JMS MDB listeners with concurrent threads that create work objects that use multiple files. If a primary key constraint violation exception occurs in this situation, update the data source configuration file to set the jta parameter to true. For example, set <datasource jta="true" jndi-name-"java:/jdbc/PegaRULES>.

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.

No support for Android versions earlier than 4.4 on mobile devices

Pega^® Platform dynamic layouts by default now use Flexbox-based rendering. As a result, mobile devices running on Android versions earlier than 4.4 are not supported in Pega Platform. Such devices cannot render correctly with Flexbox because the Pega Mobile Client includes the default stock browser on the Android operating system.

Multiple notifications are delivered for the same Pulse post

When a user posts a Pulse comment, the users who subscribe to the activity feed might receive more than one notification if the posted comment triggers several notification rules.

For example, when a user posts a comment on a case that he or she follows, any response to the comment can result in the following notifications:

• Notification when a new comment is posted on the followed case (triggers the pyAddPulsePost notification definition)
• Notification when a comment is a response to the user’s original post (triggers the pyAddPulsePost notification definition)
• Notification when the user is mentioned in the comment (triggers the pyAddUserMentionedPost notification definition)

Surveys are not compatible with prior versions of the UI Kit

Now that survey functionality is available in the Pega-Survey ruleset, some rules are no longer compatible with prior versions of the UI Kit. To ensure that your surveys are rendered correctly, update your Application form to include version 09.01 of the UI Kit.

If you cannot change the version of the UI Kit, you can override the Work-.pyCaseActionArea section in your application and update it to use the same configuration as the section in version 09.01 of the UI Kit.