Published Release Notes

Decisioning services now use default node classification

Decisioning services have been integrated with default node classification on Pega^® Platform to provide a unified way of creating and initializing services. As a result of the integration, the Data Flow service has been divided into Batch and Real Time services to better handle different types of data flow runs. You can now specify separate subsets of Data Flow nodes for batch data flow runs and real-time data flow runs to divide the workload between these two subsets.

For more information, see Node classification, Data Flows landing page, and Services landing page.

New interaction history attribute

Pega^® Platform 7.4 introduces the pySubjectType attribute that is used in interaction history aggregations. This attribute is populated for interaction history records that were created in release 7.4. For records that originated in earlier releases, the attribute must be set in the following scenarios:

• Single-level decisioning frameworks that use interaction history.
• Multi-level decisioning frameworks where interaction history is used by two or more levels of strategies that are defined on different classes.

For the single-level scenario, configure the Dynamic System Setting that sets the pySubjectType attribute when your framework reads interaction history records. The value of this Dynamic System Setting becomes the name of the customer class.

For the multi-level scenario, update the database table for all strategy levels manually. For each level, make sure that the value in the Subject Type column is set to the name of the class for the corresponding strategy. For example, the value for the top level strategy should be set to the name of the class of that strategy.

For more information about interaction history aggregations, see Data Sources landing page

For more information about multi-line strategies and contexts, see Strategy components - Embedded strategy

Mobile channel enhancements

The Mobile channel now supports several enhancements to Pega Infinity Mobile Client™ and provides custom mobile app options that are arranged in a more intuitive, consistent, and convenient layout. By default, custom mobile apps that you configure within the Mobile channel are generated with Pega Infinity Mobile Client. You can choose between a single webview web portal or a multi webview application layout, and configure such options as: bottom bar navigation rule, the bottom bar style, and the full screen search widget. You can also build a custom mobile app with Pega Mobile Client 7, or select a specific version of the client application.

For more information, see Configuring a custom mobile app.

Multiple actions triggering during intelligent email routing

Pega Intelligent Virtual Assistant™ (IVA) for Email now supports triggering of multiple actions during the intelligent routing of incoming emails, which improves the artificial intelligence capability of IVA for Email so that it is more responsive to user input. For example, you can set up intelligent routing for an Email channel to trigger multiple actions, such as creating a case and automatically replying to an email for the content that you receive.

For more information, see Intelligent email routing, Configuring routing conditions for automatic email handling, and Setting up intelligent routing in Intelligent Virtual Assistant for Email.

Facebook and Web Chatbot configuration in the preview console

When you develop a Pega Intelligent Virtual Assistant™ (IVA) for Facebook or Web Chatbot, you can now teach interactive bot conversations by chatting with the bot in the preview console and guiding the artificial intelligence algorithm to the right responses. This ability greatly accelerates conversation development and simplifies configuration, while providing the developer with more transparency in the mechanisms that produce specific responses.

For more information, see Simulating a conversation and building a chatbot runtime and Testing and building a chatbot from the preview console.

Manage access to the content in your spaces and cases

To more efficiently manage your content, you can grant access to documents only to specific space or case members in a portal that you use. Use this option to provide users with content that is tailored to their specific needs. Provide contextual and consistent documents for your users for more effective communication and case management.

• For App Studio: Adding content to a space, Creating a document.
• For Dev Studio: Adding content to a space, Creating a document.

Default support for the OAuth 2.0 framework in custom mobile apps

You can now build custom mobile apps by using Pega Infinity Mobile Client or Pega Mobile Client 7 with the OAuth 2.0 authorization code grant flow that is enabled by default. This industry-standard authorization framework increases the security of custom mobile apps. Set up your application to either redirect to a login screen of a specific identity provider, or display a selection of available identity providers upon login. Settings for authentication services are now applied automatically when you build your app. You can ensure that a custom mobile app is secure by using a protection schema, such as a biometric sensor or a custom pin.

For more information, see Build secure custom mobile apps with the OAuth 2.0 framework.

Personalize survey questions by reusing properties

Now you can create more dynamic and personalized surveys by incorporating answers to previous questions in subsequent questions. For example, you can ask users to provide their place of residence, and then reuse this data in the questions that follow. By using this feature, you create personalized surveys that are more engaging and more specific to users’ needs.

For more information, see Reusing answers in a question.

Improvements to email case triaging

Improvements to Pega Intelligent Virtual Assistant™ (IVA) for Email make the system more robust and user friendly. When you reply to emails in a triage case, you can forward the email, reply to all, and use the carbon copy (cc) and blind carbon copy (bcc) fields. You can also send Pulse messages to discuss an email case without exposing the information to external users. You are notified in the Email Manager and Case Manager portal if you receive Pulse messages. Even when an email case has been resolved and appears as read-only, you can still send Pulse messages.

For more information, see Email Manager portal and Email triage.

Create and assign tasks in Pulse

You can now create and assign tasks in Pulse for case work that needs to be completed within a specific time frame. For example, you can assign a task to yourself as a reminder to upload proof of address documents to a Car Loans case by the end of the day.

For more information, see Creating a task in Pulse, Enabling users to post messages in the activity feed.