Published Release Notes

More action types on the bottom bar

Pega Infinity Mobile Client™ now provides more flexible bottom bar configuration with a broader choice of actions, so that your apps can be more useful. For example, users can now create work items, open work items, or log out directly from the bottom bar of a mobile app.

For more information, see Configuring the bottom bar.

Support for custom database tables in external Cassandra clusters

Pega Platform™ now supports a connection to external Cassandra clusters through a dedicated Database Table data set, which reduces the need for data ingestion and export. You can use custom tables that you store in your external Cassandra cluster in data flows for accessing and saving data. You can access your custom data model by mapping the model to a Pega Platform class.

For more information, see Connecting to an external Cassandra database through a Database Table data set.

Enhanced data flow performance monitoring

The performance alert log now provides more detailed information about the data flows in your application. You can view performance details for data flows that are currently running and data flow runs that have completed successfully. You can also view a performance summary for data flow runs that are running for too long or have failed.

For more information, see:

• PEGA0082 alert: Dataflow started
• PEGA0083 alert: Dataflow complete
• PEGA0062 alert: Data flow execution time above threshold
• PEGA0072 alert: Data flow run failed

Ability to support advanced device features with Pega Infinity Mobile Client

Pega Infinity Mobile Client™ now provides a development kit that you can use to make mobile apps support advanced device features that are typically available to native applications, for example, an embedded laser scanner or a projector module, and integrate functions of external software solutions, for example, a cloud-based file storage.

For more information about enhancing mobile apps with device feature support, see the documentation for the development module in the latest Pega Infinity Mobile Client distribution package on Digital Delivery.

Support for regular performance alerts

You can now specify how often Pega Platform™ sends you performance alerts about SLA violations in data flow runs. By default, the interval is 5 seconds for single case data flows and 5 minutes for batch and real-time data flows.

The following dynamic system settings control the alert interval:

• Single case runs: dataflow/singlecase/alert/throttleTime
• Batch runs: dataflow/batch/alert/throttleTime
• Real-time runs: dataflow/realtime/alert/throttleTime

For more information, see PEGA0062 alert: Data flow execution time above threshold.

Automatic model training when mapping entities to case properties in Email Bot

You can now initiate automatic feedback to entity models in Pega Email Bot™, during manual mapping of email content to a case property.

To enable automatic feedback, you set the Work-Channel-Triage.pyIsRuntimeFeedback rule to true in Pega Platform™. By default this feature is disabled. Enabling this feature ensures that the email bot is more responsive by automatically copying detected entities, such as names, locations, dates, and ZIP codes, to case type properties of a case type.

For more information, see Email triage, Email channel NLP model and Enabling the NLP model training for the email channel.

Case-insensitive filtering in reports

Filtering in reports is now case-insensitive, improving the reporting and searching experience. You can turn off case-insensitive filtering, for example, by using an activity. You might want to do this if your index is too big or if the length of time it takes for indexing impacts performance.

For more information on report filtering, see Editing filter conditions.

Add subspaces within spaces

You can now create subspaces within spaces. By adding a subspace, you can collaborate on a subtopic that is related to the topic of the parent space. For example, you can create an Annual Day subspace within the Events space.

For more information, see Creating a subspace.

PATCH support for REST integrations

REST connectors and REST services now include support for integrating with REST APIs that require using the PATCH method. REST integrations that support the PATCH method allow you to make partial updates to individual resources while retaining data that does not require an update. With PATCH support, you no longer need to write complex custom code to integrate with services that require using the PATCH method.

For more information about REST integrations, see Connect REST form - Completing the Methods tab.

Configure REST connectors for standard-compliant endpoints

REST connectors now support all standards-compliant endpoint URLs, regardless of how those URLs use query parameters.

This URL support allows you to do the following actions:

• Include repeated query string parameters in a URL.
• Omit a query string parameter if the value of the parameter is empty when you send a request.
• Apply appropriate encoding for different URL components.

For more information about REST connectors, see Connect REST form.