Published Release Notes

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.

Enhanced SLA settings in App Studio

You can now reuse existing service-level agreements for assignments and approvals in App Studio without switching to Dev Studio. For example, you can select an action that the system performs when a task goal or deadline is past due, such as reassigning the task to a different user.

For more information, see Setting goals and deadlines for task completion and Defining an escalation action for an incomplete task.

Support for rich HTML text in IVA for Email

Pega Intelligent Virtual Assistant™ (IVA) for Email now supports rich HTML text in email conversations, which enhances the overall user experience. You can enable this option in the Email channel configuration in IVA for Email to display rich text in email conversations for case triaging. Natural language processing (NLP) analysis works flawlessly in scenarios for all email content that contains rich HTML text.

For more information, see Enabling rich HTML text in emails.

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.

Additional case settings in App Studio

You can now make it easier to distinguish your case type from other case types by customizing its icon and selecting a unique case ID prefix in the General case settings.

You can also access Locking and Notifications case settings in App Studio without switching to Dev Studio.

For more information, see:

• Changing the case ID format
• Changing the case icon
• Managing concurrent access to a case
• Enabling case notifications

Configure search for duplicate cases in the step property panel

You can now configure the search for duplicate cases in the step property panel. Save time by specifying search criteria that effectively identify potential duplicate cases.

At run time, make sure that each case represents a unique request by deciding whether to close the case as a duplicate, based on the criteria by which the system marked the case as a potential duplicate, for example, a matching email address.

For more information, see:

• For Dev Studio: Finding duplicate cases
• For App Studio: Finding duplicate cases

Visualize tasks more clearly with the task board view

In spaces and other contexts, you can now monitor and track the resolution of cases by using the task board view. This view groups tasks into columns by status to provide a visual overview for all members of a space. By default, the task board view is enabled in spaces, but you can enable it in any context to meet your needs.

For more information, see Monitoring and tracking cases (for App Studio) or Monitoring and tracking cases (for Dev Studio).

Rule revalidation after updating properties without restarting nodes

When you update certain property attributes, such as a property's maximum length, rule types that reference the property might not reflect the change. You do not always have to restart nodes to revalidate the referencing rules when they cannot be resaved, for example, when they are in a locked ruleset. For Pega Platform™ 8.1 and later, for non-stream rules, such as activities, data transforms, and so on, use the reassemble API in Admin Studio or truncate the assembled classes table.

For stream rules, such as sections, harnesses, paragraphs, and so on, reassemble the rules and restart the nodes. For more information, see More about properties.

For previous versions of Pega Platform, use the System Management Application (SMA) to revalidate stream and non-stream rules.

Deprecated support for passing symbolic index as strings to value lists and page lists

Starting with the next release after Pega Platform™ 8.2, passing symbolic indexes as strings in parameters, properties, and string literals to both value lists and page lists will no longer be supported. The following examples show the syntax that still works in Pega 8.2, that will not work in the next release:

myPageList("<LAST>")

and

param.str = "<LAST>"
myPageList(param.str)

The following example shows syntax that currently is not supported and gives a validation error. This syntax will also not work in future releases.

param.str = <LAST>
myPageList(param.str)

To avoid issues after upgrading to Pega 8.3, refactor all occurrences of this syntax in your code. For instructions on how to find occurrences of this syntax in your code, see Refactoring unsupported symbolic index syntax for value lists and page lists.

For more information about the correct use of symbolic indexes, see Symbolic indexes – APPEND, CURRENT, INSERT, LAST, and PREPEND.

Make important content visible by promoting spaces

Now you can make highly relevant content more visible and more easily accessible with promoted spaces. Highlight promoted spaces on a separate tab in spaces to ensure that the most relevant content is quickly available and clearly organized. Promoted spaces are available for every user; however, only users with Super Admin privileges can promote a space.

For more information, see Granting Super Admin privileges.