Published Release Notes

Support for OAuth 2.0 authorization in Pega Platform REST services

Pega^® Platform REST services now support OAuth 2.0 authorization that uses federated authentication with SAML 2.0-compliant identity providers (IDPs). The OAuth 2.0-based authorization can be configured to use the SAML2-bearer grant type with a SAML token profile. This configuration is used when a resource requestor is authenticated by using a SAML2.0-compliant IDP.

For more information, see Security rules and data.

Privilege inheritance support through access roles

Privilege inheritance simplifies the process of defining privileges that are relevant in multiple classes. When determining whether a user should be granted a named privilege that allows a type of access to a class, Pega^® Platform searches for Access of Role to Object (Rule-Access-Role-Obj) rules that are relevant to the target class and to the access roles listed in the user's access group, and considers the privileges granted or denied in those rules. When privilege inheritance is enabled within an access role, the search for relevant Access of Role to Object rules begins with the target class and, if necessary, continues up the class hierarchy until a relevant rule is found.

For more information, see Privilege inheritance for access roles.

Use Kafka data sets in Pega Decision Strategy Manager

You can create Kafka data set rules to connect to an external Apache Kafka server cluster and use this data set in decision management for processing real-time streaming data. Integrating Kafka data sets into complex event processing (CEP) as part of Event Strategy rules provides a fault-tolerant and scalable solution for processing real-time data feeds.

For more information, see Kafka data sets in decision management.

Send event notifications in Pega Platform

You can configure applications to notify users of case changes or other significant events that occur in an application. Use notifications to engage application users by providing key updates that might be of interest to them.

You can deliver notifications over the default web gadget and email channels or use a custom channel that you created. You can configure multiple web gadgets to display different kinds of notifications. The email channel supports notification frequency of instant, daily, or weekly.

Application users can set their own notification preferences in the run-time portals or override the set preferences for a specific case type instance.

For more information, see Sending event notifications and Management of user notification preferences.

Reused forms support fields that can be modified

Now, you can choose whether the fields in an embedded form are read only or can be modified at run-time. You can set the reused form to Auto, which maintains the display mode (read only, required, optional) set for each field. Reusing a form reduces development time and maintains a consistent layout for a set of fields.

For more information, see Reusing a form.

Out-of-sequence processing added to steps in a life cycle

In Pega Express, you can now add a step to the life cycle of a case type that moves a case from one stage to another. By revisiting or skipping a stage, you can support out-of-sequence processing in a case.

For more information about supporting dynamic stage sequences, see Moving a case to a different stage.

Push notifications added to steps in a life cycle

In Pega Express, you can now add a step to the life cycle of a case type that pushes a notification to users on mobile devices when a case requires an action, such as approval or review. By using an event-driven model to send messages, you can ensure that cases are resolved quickly.

For more information about push notifications, see Sending a push notification from a case.

Message posting added to steps in a life cycle

In Pega Express, you can now add a step to the life cycle of a case type that updates the social activity stream of a case. By posting information as it becomes available, you can inform case workers and provide a visible discussion thread for stakeholders.

For more information about message posting, see Posting messages to a case.

Stage progression in a life cycle includes alternate paths

In Pega Express, you can now add alternate stages to the life cycle of a case type. You can also change the type of a stage from primary to alternate, or alternate to primary. By using different types of stages, you can separate expected behavior from the exceptions in your application.

For more information about stages, see Defining a life cycle for a case type.

Use definition classes to create Decision Data rules that contain text analytics records

Use the dedicated definition classes to create Decision Data rules that contain all the types of records that are used in text analytics, such as taxonomies, lexicon, entity extraction rules, and so on. By using these definition classes, you can quickly create, update, and manage the text analytics records in your application.

For more information, see Definition class of text analytics Decision Data rules.