Kafka data set enhancements
Valid from Pega Version 8.6
The Kafka data set is a high-throughput and low-latency platform for handling real-time data feeds that you can use as input for Pega Platform event strategies.
For better integration of Pega Platform with externally hosted Kafka, the following enhancements are implemented:
- Support for Kafka message keys and headers - extended values data format (JSON Data Transform, Apache Avro)
- Custom value processing
- Configuring topic names by using Application Properties
- Data-Admin-Kafka enhancements - supporting a wide range of connection properties
For more information, see Improve your Kafka data set with new enhancements.
Case outcome predictions in case types
Valid from Pega Version 8.6
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
Valid from Pega Version 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.
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.
Facebook and YouTube data sets are deprecated
Pega Platform™ no longer supports the data set types in the Social category:
- Facebook data sets
- YouTube data sets
These features are deprecated and will be removed in future Pega Platform versions. Do not create any data sets using the Facebook or YouTube types.