Text predictions simplify the configuration of text analytics for conversational channels
Valid from Pega Version 8.6
Enable text analytics for your conversational channels, such as email and chatbot, by configuring text predictions that manage the text models for your channels. This new type of prediction in Prediction Studio consolidates the AI for analyzing the messages in your conversational channels in one place and replaces the text analyzer rule in Dev Studio.
Through text predictions, you can efficiently configure the outcomes that you want to predict by analyzing the text in your channels:
- Topics (ticket booking, subscription cancellation, support request)
- Sentiments (positive, neutral, negative)
- Entities (people, organizations, airport codes)
- Languages
You can train and build the models that predict these outcomes through an intuitive process, and then monitor the outcomes through user-friendly charts.
For more information, see Predict customer needs and behaviors by using text predictions in your conversational channels.
Upgrade impact
Channels that you configured with text analyzers in the previous version of your system continue to work in the same manner after the upgrade to the current version. When you edit and save the configuration of an existing channel, the text analyzer rule is automatically upgraded to a text prediction. The associated text prediction is now an object where you can manage and monitor the text analytics for your channel. When you create a new channel in the upgraded system, the system automatically creates a text prediction for that channel.
What steps are required to update the application to be compatible with this change?
- Enable the asynchronous model building and reporting in text predictions through job schedulers that use the System Runtime Context (SRC) by adding your application to the SRC.
For more information, see Automating the runtime context management of background processes. - Enable model building in text predictions by configuring background processing nodes.
For more information, see Assigning decision management node types to Pega Platform nodes.
External data flow rules are removed
Valid from Pega Version 8.6
In previous versions of Pega Platform™, you could configure data flows to run in an external Hadoop environment. The external data flows functionality was deprecated and hidden from view in Pega Platform 8.5. The functionality has been now removed and is no longer available in Pega Platform 8.6.
For more information, see External data flow rules are deprecated.
Naming pattern changed for file data sets
Valid from Pega Version 8.6.3
File data sets are used to import from and export data to a file repository. In case of data export, prior to version 8.6.3, the first file exported had the same file name that was provided by the user in the data set, and any subsequent file exported to the repository had a unique identifier appended to it. Starting in Pega Platform version 8.6.3, each file has a unique identifier, automatically generated based on the data flow node, thread ID, and timestamp.
Upgrade impact
If your process to consume output files expects files with a specific name, it may not be able to process the resulting files correctly.
What steps are required to update the application to be compatible with this change?
If you have configured the process before updating to Pega Platform version 8.6.3, but the exported files are no longer recognized by downstream processing logic after the upgrade, ensure that the downstream tool is configured to recognize the files by a pattern rather than the full name. For example, when referring to files exported to the repository, use the * character to indicate a pattern instead of using the full file name. For example, use Export*.csv to refer to the files.