Flexible inputs in strategies
Valid from Pega Version 7.1.6
Decision parameters allow business users to influence the decision through flexible inputs that do not require changing strategies. System architects use extension points to configure the data model and user interface supporting decision parameters. Decision parameters are used in strategies, and changes to the values of decision parameters become immediately available without requiring any changes to the strategy.
The rule pxRunDecisionParameters supports the use of decision parameters through activities.
Enable business users to own parts of an enterprise application
Valid from Pega Version 7.1.6
Decision Manager functionality allows business users to own parts of an enterprise application within the boundaries defined by IT. PegaDM includes the Pega-DecisionManager ruleset that supports this functionality.
System architects define the boundaries for business users in the Decision Manager portal using revision management and proposition authorization facilities in Designer Studio. Access control is provided through custom roles, which system architects can create based on granular privileges. The Decision Manager portal provides business users with a controlled environment for the workflow, and the activities necessary to address the objectives of a revision.
Predefined inputs when designing and testing strategies
Valid from Pega Version 7.1.6
External input settings allow for propagating results to other strategies, providing strategy designers with a mechanism to reuse strategies and test strategies with predefined inputs.
Design segmentation trees in strategies
Valid from Pega Version 7.1.6
You can include the traditional segmentation tree pattern in your strategies using the following features:
- Exclusion components to conditionally stop the propagation of decision results.
- Split components to branch the decision results according to the percentage of cases covered by the result.
- The Otherwise label for component connections where one of the outgoing connections has a defined label.
Simplified Adaptive Decision Manager Deployment
Valid from Pega Version 7.1.6
The Adaptive Decision Manager (ADM) server relies on automatic detection of the database dialect. This simplifies the number of deployable archives used to set up the ADM service.
Cumulative calculation in strategies
Valid from Pega Version 7.1.6
Iteration components provide strategies with a mechanism to perform cumulative calculations.
User interface distortions in the Decision Manager portal
Valid from Pega Version 7.1.6
By default, the New Application wizard in Pega 7.1.6 configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Decision Manager portal. Both applications created in previous maintenance level updates and applications created in Pega 7.1.6 that do not include the UI-Kit-7 dependency are not impacted by this known issue.
Workaround:
- Open the application record.
- In Application Rulesets, remove UI-Kit-7.
- Save the application record.
User interface distortions in the Predictive Analytics Director portal
Valid from Pega Version 7.1.6
By default, the New Application wizard configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Predictive Analytics Director portal. Applications created in maintenance level updates previous to Pega 7.1.6, and applications that do not include the UI-Kit-7 dependency, are not impacted by this known issue.
Workaround:
- Open the application record.
- In , remove UI-Kit-7.
- Save the application record.
Conversation flow and smart shapes for the Digital Messaging chatbots
Valid from Pega Version 8.6
When creating Pega Intelligent Virtual Assistant™ (IVA) for Digital Messaging, chatbot developers can now use new conversation smart shapes in a dedicated flow, making the design process simpler, more robust, and intuitive. With the new smart shapes, the chatbot displays text messages or asks questions to users in one of several ways. In addition, developers do not have to create additional rules, switch tabs, or perform manual validation. You can associate the conversation flow that you create for your IVA with a business case, use the flow on its own, or reuse it in another conversation flow, improving the overall chatbot design process.
For more information, see Adding a stand-alone conversation process for a conversational channel, Adding a case type conversation process for a conversational channel, Editing the conversation smart shapes and Flow shapes.
Ability to forward emails in triage cases
Valid from Pega Version 8.6
When working on customer emails in the Email Manager or Case Manager portal, customer service representatives (CSRs) can now forward emails to additional stakeholders, for example, third-party vendors or sellers. As a result, CSRs that work with Pega Email Bot™ save time, improve responsiveness to customer inquiries, and make email triaging more efficient. The email bot keeps each forwarded email conversation in a separate email thread from the customer conversation, making the system more consistent and secure.
For more information, see Communicate with stakeholders on a customer query by forwarding emails and Forwarding emails to other stakeholders for an email bot.