Published Release Notes

Resolve Job Scheduler and Queue Processor rules with the AsyncProcessor requestor type

Use the new AsyncProcessor requestor type to define a default dynamic context to resolve background rules such as Job Scheduler and Queue Processor rules. Switch to an application-based context after you create your own access groups, to resolve only the rules that are included in your application.

For more information, see AsyncProcessor requestor type.

Relevant records management shows more information

Relevant records for a class now include more information that you can use to manage the records for your application development. As a result of these enhancements, you can:

• View inherited and inactive relevant records for the specified class.
• Mark specific records as active or inactive for the specified class.
• Mark specific records as relevant on the rule form.

You can use these new details to filter the list of relevant records for a class on the Relevant Records tab of the selected class. For more information, see Managing relevant records and Marking records as relevant records.

Upgrading Adaptive Decision Manager data mart tables might fail

Issue: Upgrade from 7.3 to 7.3.1 fails if the data contained in the pxInsName column of the PR_DATA_DM_ADMMART_PRED_FACT table is longer than 128 characters.

Reason: During the Pega Platform™ upgrade from 7.3 to 7.3.1, data in the Adaptive Decision Manager (ADM) data mart tables is migrated from the PR_DATA_DM_ADMMART_PRED_FACT table to the PR_DATA_DM_ADMMART_MDL_FACT table. In Pega 7.3.1, ADM uses only the PR_DATA_DM_ADMMART_MDL_FACT table where the pxInsName property can store values that are 128 characters long. In Pega Platform 7.3, the pxInsName property in the PR_DATA_DM_ADMMART_PRED_FACT table can store values that are 255 characters long. If the pxInsName property contains values that are longer that 128 characters, the upgrade fails.

Resolution: Issue an ALTER TABLE statement to change the pxInsName column size to 255 characters and resume the upgrade. For example:

ALTER TABLE rules.pr_data_dm_admmart_pred ALTER COLUMN pxInsName TYPE varchar(255);

For more information, see Adaptive Decision Manager data model.

Support for when rule in offline-enabled applications

You can use when rules in offline-enabled applications without creating custom JavaScript code. Using when rules reduces the offline-enabled application implementation time by further automating case processing in offline mode and deriving the logic directly from the model. No additional configuration is required to use when rules in offline mode.

For more information, see When rule support in offline mode.

Case type landing page is created automatically

When you create a case type, a landing page is created automatically. You can add this page to the main menu, operator menu, and mobile tabs. You no longer need to create this page manually.

Support for an external Elasticsearch cluster for on-premises deployments

On-premises customers can configure an Elasticsearch cluster that is external to the Pega Platform™ by using client-server mode. Using an external search configuration makes Elasticsearch more highly available and scalable. 

You can view the status of your external Elasticsearch service on the Search landing page. For more information, see link to Viewing the status of an external search service.

Define time conditions for pausing a process in App Studio

You can now pause a process in App Studio until a date or time is reached or a certain amount of time has passed. By defining the conditions that pause a process, you can create dependencies among cases in your application.

For more information, see Pausing a process in a case.

Customize the subject line for case emails

You can now customize the subject line for emails that are sent from cases when an assignment is routed to a worklist and when you configure the Send Email shape. You can reference field names in the subject line to make it more meaningful. By customizing the subject line, you can call attention to cases that require action.

For more information, see:

• App Studio – Enabling case notifications and Sending email from a case
• Dev Studio – Enabling case notifications and Sending email from a case

Additional adaptive model predictors based on Interaction History

Customer interactions are now automatically used in adaptive models to predict future customer decisions. For example, a phone purchase registered in Interaction History allows an adaptive model to predict that a customer is more likely to accept supplementary coverage for a new device. Such interactions, collected in a predefined Interaction History summary, are applied as an additional set of predictors in an adaptive model.

The aggregated Interaction History summary predictors are enabled by default for every adaptive model configuration.

For more information, see Enabling Interaction History predictors for existing adaptive models.

Update text analytics models instantly through an API

Use the pxUpdateModels API to automatically retrain text analytics models for which you gathered feedback as a result of the pxCaptureTAFeedback activity. The pxUpdateModels API provides an option to update the model with the latest feedback without having to open Prediction Studio. Instead, you can use the activity from your application, for example, through a button control.

For more information, see Feedback loop for text analytics.