Published Release Notes

New alert for job scheduler activity that exceeds a time threshold

Pega Platform™ now saves the PEGA0130 alert in the performance alert log at the time that a scheduled job exceeds the configured threshold value. To identify performance issues with long-running processes, you can monitor the log for the alert while the job scheduler runs.

The alert is enabled by default. You can change the default threshold value or disable the alert in dynamic system settings.

For more information, see PEGA0130 alert: Current Job Scheduler run is taking too long.

Support for calling a data transform from a case life cycle in App Studio and initializing data at case creation

You can now call a data transform from a case life cycle in a low-code way in App Studio. For example, when a customer wants to order the same product again, your application can reuse the shipping information from their previous order. Additionally, by configuring data initialization for a case type, you can prepopulate fields at case creation. For example, an application for a delivery service can apply the customer's preferred delivery options when a new case starts. These enhancements save time for developers because the system can initialize data and prepopulate fields in a case by reusing existing logic, and for customers, who do not need to manually enter their details every time.

For more information, see Calling a data transform from a case and Initializing data at case creation.

Data propagation for questionnaires in case types

Pega Platform™ now provides a tool to prepopulate answers in a questionnaire that runs in a case by propagating data from a parent case. At run time, specified questions in a questionnaire that users complete as part of case processing, can display answers by using information that users already provided in the parent case. As a result, you speed up the development of your application and help users process cases and complete questionnaires faster.

For more information, see:

• Deliver user-friendly questionnaires by prepopulating answers (8.6)
• Running a questionnaire in a case

Improved indexing performance by gradual retrieval of data

Search functionality in Pega Platform™ versions from 8.4.5 to 8.6 now includes the option to improve indexing performance when reading query results from a large table in a database. For example, to load the recommended 50 records at a time, in the Pega-SearchEngine ruleset, create the indexing/distributed/fetchsize dynamic system setting, and set the value to 50.

Creating the fetchsize dynamic system setting ensures that your system does not crash while indexing classes with numerous instances.

For more information, see Creating a dynamic system setting.

Case outcome predictions in case types

Pega Platform™ introduces the use of machine learning and AI in Case Designer. You can now use predictions in case types, both in App Studio and Dev Studio. By using predictions, your application can predict various outcomes, such as the possibility of reaching a positive or negative case resolution, so that you can prioritize work, route cases according to risk, or optimize the case flow in other ways. You can use predictions when you create conditions in the condition builder, for example, when you define a business logic for routing assignments. 

For more information, see:

• Prioritize and route case work by predicting case outcomes 
• Predicting case outcome
• Creating predictions for case management

Virtual questions deprecated in 8.6

Following the improvements in Pega Intelligent Virtual Assistant (IVA), the creation of virtual questions is now deprecated and planned for removal. To avoid additional effort during updates to future releases, do not use deprecated features. For optimal application performance and efficient development of conversation processes, you now collect information from users by using the Ask a question smart shape.

For more information, see Adding a case type conversation process for a conversational channel and Asking a question in a case.

Data model inheritance does not depend on ruleset context

Search and Reporting Service (SRS) in Pega Platform™ 8.6 now provides an improved method of synchronizing data model by distinct users. In applications built on earlier versions of Pega Platform, some users might encounter difficulties in indexing data. Now, the data model that the system sends to SRS does not depend on access privileges. With this enhancement, each user of your application is eligible to synchronize data.