Published Release Notes

Configure search for duplicate cases in the step property panel

You can now configure the search for duplicate cases in the step property panel. Save time by specifying search criteria that effectively identify potential duplicate cases.

At run time, make sure that each case represents a unique request by deciding whether to close the case as a duplicate, based on the criteria by which the system marked the case as a potential duplicate, for example, a matching email address.

For more information, see:

• For Dev Studio: Finding duplicate cases
• For App Studio: Finding duplicate cases

Visualize tasks more clearly with the task board view

In spaces and other contexts, you can now monitor and track the resolution of cases by using the task board view. This view groups tasks into columns by status to provide a visual overview for all members of a space. By default, the task board view is enabled in spaces, but you can enable it in any context to meet your needs.

For more information, see Monitoring and tracking cases (for App Studio) or Monitoring and tracking cases (for Dev Studio).

Make important content visible by promoting spaces

Now you can make highly relevant content more visible and more easily accessible with promoted spaces. Highlight promoted spaces on a separate tab in spaces to ensure that the most relevant content is quickly available and clearly organized. Promoted spaces are available for every user; however, only users with Super Admin privileges can promote a space.

For more information, see Granting Super Admin privileges.

Support for predictive models in PMML version 4.4

Pega Platform™ now supports the import of predictive models in Predictive Model Markup Language (PMML) version 4.4. With this feature, you can import PMML models that use the anomaly detection algorithm.

For a list of all supported PMML models, see Supported models for import. 

Support for advanced validation of embedded and referenced data

To help you define validation conditions for a broader range of use case scenarios, Pega Platform™ now supports stage entry validation for embedded fields in the form of a validation matrix. You can now define validation conditions for both field groups and field group lists, and easily navigate between them. You can also select any fields and when conditions while building a condition for both field-level and stage-level validation.

For more information, see Validating field values for stage entry.

Complete email and notification approval in App Studio

App Studio now supports complete email approval configuration directly in the Case Designer. Email approval settings now include composing a new message or selecting a template, saving templates to a library for future reuse, and adding attachments to an email. Additionally, you can now send the approval as a push notification to mobile users. With full configuration of email approval in App Studio, you save time and create unique and personalized email messages and push notifications in a no-code, intuitive way. 

For more information, see Obtain approvals from email and push notifications from App Studio (8.5), Requesting approval by email and push notification.

Business logic routing of approval steps

Pega Platform™ now supports routing of approval steps by applying business logic, in both App Studio and Dev Studio. Business logic uses a set of conditions to determine the most appropriate worker to approve a case by routing the approval based on defined conditions. For example, in a loan request case, the application can route the approval step to a manager if the importance of the case is set to high. For greater accuracy, business logic can also use skill set, availability, and workload to determine the appropriate worker. With business logic routing, you increase work efficiency and speed up case resolution.

For more information, see Determine a relevant case approver by using business logic (8.5), Requesting approval from users.

Limits on active data flow runs

You can now configure a maximum number of concurrent active data flow runs for a node type. Set limits to ensure that you do not run out of system resources and that you have a reasonable processing throughput. If a limit is reached, the system queues subsequent runs and waits for active runs to stop or finish before queued runs can be initiated, starting with the oldest.

For more information see, Limit the number of active runs in data flow services (8.5).

Upgrade impact

If you have many data flow runs active at the same time, you might notice that some of the runs are queued and waiting to be executed.

What steps are required to update the application to be compatible with this change?

You do not have to take any action. After the active runs stop or finish, the queued runs start automatically. The default limits are intended to protect your system resources, and you should not see a negative impact on the processing of data flows. However, if you want to allow a greater number of active data flow runs to be active at the same time, you can change the limits. For more information, see Limiting active data flow runs.

Support for Apache HBase 2.1 and Hadoop 3.0

Support for these versions extends Pega Platform™ compatibility with HBase releases to ensure that your database implementations integrate seamlessly with Pega Platform.

Pega Platform now supports:

• Apache HBase 2.1 for the HBase data set
• Apache Hadoop Distributed File System (HDFS) 3.0 for the HDFS data set

For more information, see Enhance your data sets with Apache HBase 2.1 and Hadoop 3.0 (8.5).

Enhancing your revision management process with Deployment Manager pipelines

Pega Platform 8.5 offers improved synergy between revision management and the automated deployment process provided by Pega's Deployment Manager 4.8 pipelines. Use Deployment Manager 4.8 to increase the efficiency of business-as-usual application changes and automatize the deployment of revision packages.

For more information, see Managing the business-as-usual changes.