Published Release Notes

Team management

As a case manager or manager of a team, you can manage all your teams and direct reports on the My Teams page in Case Manager. You can create teams or delete existing ones, as well as update team membership and work queues assigned to the team. You can also update and manage workload, time off, and skills information for individual team members. Social collaboration through Pulse is also available for both teams and individual users.

For more information, see Managing team information and work queues.

Enhanced data modeling

You can now create data types quickly in Pega Express. Use the enhanced Data Designer user interface to define the data model for your data types. More field types have been added, and they are categorized as simple, fancy, and complex to meet your data modeling needs.

For more information, see Data Designer enhancements.

Child case queries performance can be slow

Some customers have reported that performance is slow when they execute queries on child cases. This issue is often indicated by PEGA0005 (query time exceeded limit) alerts that can be correlated to these queries in the logs. To resolve the issue, add a database index to each of your work tables by using a multicolumn index on the pxCoverInsKey, pxObjClass, and pyStatusWork columns.

See Performance improvements for child case queries.

Updates to the Data Page rule form

You can use the enhanced Data Page rule form to specify the name of a source system in the System name field in the Data sources section. This field represents the name of the system that is associated with a data source. For example, if your data source is a REST connector that connects to an external weather service such as Google Weather API, you can enter Google Weather in the System name field for the data source. The system name is used to display the source systems for a data type on the External Data Entities landing page.

For more information, see Viewing external data entities.

Verify ML Readiness error: Upgrades from Pega 7.1.0 through 7.1.8 do not replace nonversioned rules

Upgrading from any Pega 7 Platform version between Pega 7.1 and Pega 7.1.8 to Pega 7.2 does not automatically replace nonversioned rules. If you revalidated and saved a Pega 7.1.x rule after the timestamp on the Pega 7.2 version of the rule, upgrading to Pega 7.2 does not overwrite the saved rule. You might see either of the following behaviors:

• The upgrade fails with the following error message:
  Verify ML Readiness
• The upgrade succeeds, but you might be unable to open changed rule forms.

If the upgrade fails, see the Pega 7 Platform Upgrade Guide to force the upgrade.

This known issue does not affect Pega 7.1.9. After the upgrade has finished, apply Hotfix 27288. For information about obtaining and applying hotfixes, see Hotfix Manager.

Unused agents run in background

The Update PegaRULES database table statistics agent and the Collect PegaRULES database blob size statistics agent have been added to support future development. These agents run in the background, but they do not do anything. You can, but do not need to, disable them from the Edit Agent Schedule landing page.

For more information, see Agent Schedule form - Completing the Schedule tab.

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.