Published Release Notes

Conversion of single-step assignments is no longer required

You no longer need to create a single-step assignment in a case type and then convert it to another supported step type. Instead, you can use the + Add step option in Case Designer to add any step type directly to a process in a stage. This change delivers a more consistent experience to users who are working in Case Designer and Process Modeler.

The following table lists the step labels in Case Designer that were updated to support this change.

For more information, see Adding a step to a process in a stage.

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.

New options to manage proposition validity

Manage your decisioning strategy more effectively with proposition validity settings. You can now set your propositions as always active, inactive, or active only within a defined time period. Setting a validity period for your propositions helps you to plan your strategy and automatically activate or deactivate propositions in the future.

For more information, see Proposition validity.

Ability to import data into a Pega Cloud database

You can export a custom Pega 7 Platform database table into a CSV file and import it into a Pega Cloud database or other Pega 7 Platform database by using the Data Upload utility. This utility is available only for Postgres databases and tables that do not contain BLOB columns. This utility is useful, for example, for updating a product catalog that is used in a Pega Cloud application.

For more information, see Importing data into a Pega Cloud database.

Ability to schedule schema updates for Pega Cloud

You can schedule BLOB size and table statistic updates to database schemas to run automatically by using agents. Scheduling schema updates is useful for performance monitoring and tuning in the Pega Cloud. This feature is available only for customers who use a Postgres database.

There is an agent for updating the average and maximum BLOB sizes, and an agent for updating table statistics. Each agent can be configured separately for each schema. You can configure whether to schedule the agent to run daily or weekly. You can deactivate a running schedule on the Schema Tools landing page by clicking Designer Studio > System > Database > Schema Tools. From the Schema Tools landing page, you can configure more complex scheduling on the Edit Agent Schedule landing page. In addition, you can configure these agents by using Dynamic Data System Settings.

For more information, see Scheduling schema updates.

BIX performance improvements for CSV output in the Pega Cloud

BIX performance has been enhanced to download up to 25 GB of data per hour for extracts from a BLOB-less class table for CSV output. This high-throughput option is available only for Pega Cloud instances that use a Postgres database. This option is used automatically for these types of extracts.

When this option is used, the –x and –c command-line options for BIX are not supported, and the checkSum field in the manifest summary is not populated. If you need these options, you can revert to the previous implementation by using a setting in the prconfig.xml file.

For more information, see BIX high-throughput data downloads in the Pega Cloud.

Push notification delivery to multiple devices

Push notifications sent from the Pega 7 Platform are now delivered to all devices on which a user is logged in to your custom mobile app, regardless of the device platform. You can either send push notifications from the Push Console to all users who have your application installed on their devices, or configure your application to send push notifications to indicate that an action might be required, a status update is available, or a case was approved.

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.