Conditional paths added to case life cycle
Valid from Pega Version 7.3.1
You can now add a conditional path to a process in the life cycle of a case. By defining the decisions that cause a process to follow different paths, you can create cases that support more than one outcome.
For more information about conditional paths, see Conditional paths in a case life cycle.
Receive and reply to push notifications for Pulse messages
Valid from Pega Version 7.3.1
You can now receive push notifications on your mobile device when another user references you in a Pulse message or likes your messages in a Pulse conversation. You can both receive and reply to the push notifications that you get when another user posts on your profile, adds messages to a Pulse conversation in which you are involved, or posts comments on a case that you are following. To receive push notifications, select mobile push as a notification channel when you configure your notification preferences.
For information about Pulse enhancements, see Pulse enhancements for social collaboration.
Integrate the intelligent interaction activity for text analytics into your application
Valid from Pega Version 7.3.1
Employ text analytics and machine-learning capabilities in multichannel applications by integrating the pyRunInteraction activity for content parsing and analysis. By calling this activity, you can automatically analyze any incoming text data, such as instant messages, posts, emails, and so on, to detect sentiments, categories, entities, or intents that can help you with automatic case creation and routing. For example, you can use this activity to populate case properties based on detected entities such as customer name, email address, and account number.
For more information, see Intelligent interaction in text analytics.
Update text analysis models during every interaction
Valid from Pega Version 7.3.1
While interacting with your customers through text-based communication channels (such as a Facebook chatbot or email), you can use an activity to provide feedback to a text analysis model by manually assessing whether the entities, categories, intents, and sentiments in the analyzed text were assigned to the expected class. By using this feedback input as training data, you can ensure that the accuracy of your text analytics models continuously improves.
For more information, see Feedback loop for text analysis.
Build predictive models with the genetic algorithm
Valid from Pega Version 7.3.1
A genetic algorithm solves optimization problems by creating a generation of possible solutions to the problem. In Pega® Platform you can utilize the functionality of genetic algorithms by using the genetic algorithm model in the Analytics Center portal. With this type of predictive model, you can create highly predictive, non-linear models by selecting the best performing model from the last generation.
For more information, see Creating models and Creating a genetic algorithm model.
Use of the @java function in expressions is deprecated
Valid from Pega Version 7.3.1
Use of the @java function in expressions is deprecated. Use a utility function or other product feature instead.
For more information about expressions, see Building expressions with the Expression Builder.
Change passwords from Pega Mobile Client
Valid from Pega Version 7.3.1
You can now change your Pega® Platform password from a mobile device. After your password expires and you try to log in to a custom mobile app, Pega Mobile Client lets you define a new password and verifies it against active password policies.
For more information, see Enabling security policies.
Advance cases from a push notification screen
Valid from Pega Version 7.3.1
You can now approve and reject Pega® Platform cases from your mobile device without opening a custom mobile app. Push notifications that you receive on a mobile device now display buttons that allow you to advance a case.
For more information, see Notifications.
The Run Data Flow shape replaces the Run Interaction shape
Valid from Pega Version 7.3.1
The Run Interaction shape in flows has been replaced by the Run Data Flow shape to introduce a consistent way of making decisions and capturing responses. You can now run a single-case data flow by referencing the data flow in the Run Data Flow shape. The data flow must have an abstract input and abstract or dataset output.
For more information, see Running a decision strategy from a flow, About Data Flow rules and Interactions in flows are no longer supported by the Run Interaction shape.
Interactions in flows are no longer supported by the Run Interaction shape
Valid from Pega Version 7.3.1
The Run Interaction shape in flows has been replaced by the Run Data Flow shape, which supports running a single case data flow with a strategy. Flows that include the Run Interaction shape continue to work; however, you must now use the Utility shape to reference any new interactions that you create.
For more information, see Running a decision strategy from a flow and About Interaction rules.