Published Release Notes

Authenticate users in processes with a JSON Web Token

You can generate and process a JSON Web Token (JWT) in Pega^® Platform to secure communications in Pega Platform applications. JWTs are intended to securely transmit small amounts of information between two parties. Because the JWT is signed, the integrity of the information is assured. The contents of the JWT can be used to authenticate a user or to exchange information.

For more information, see Token Profile data instance.

Automatically process cases with SharePoint

You can now use Microsoft SharePoint Online to store and source case and Pulse attachments and to store and source attachments during automated case processing. Users only have to provide authentication and authorization details the first time they access SharePoint Online or when the trust has expired. The authentication profile must be OAuth 2.0 with a grant type of authorization code. The SharePoint Online component can be downloaded from Pega Exchange. For more information, see Downloading and configuring pluggable content management components.

Flexbox support for all default layouts

To improve scalability, Pega Platform supports flexbox-based layouts by default in all its screen and column layouts and layout groups. You can convert existing layouts to flexbox-based layouts by selecting the Optimized code option on the Presentation tab of the layout.

For more information, see Screen Layout Properties.

Ability to set default values when importing data

You can now set default values for data that you import for a data type from a .csv file. By setting defaults, you can ensure that even when the .csv file data is incomplete, all of the data is imported. In addition, you can set default values for custom fields that do not have a matching source column in the .csv file. This feature is available for the Add and update and Add only import options. For mapped fields, the default value is used for new records if the source field is blank, and for existing records if both the source and target fields are blank. For custom fields, the default value is used for new records if a default value is provided, and for existing records only if the target field is blank.

For more information, see Importing data for a data type.

Analyze intentions in text analytics

You can now analyze text content to determine whether it contains any underlying intention. Through intent analysis, you can determine whether your customers are likely to continue subscribing to your services, want to know more about your products, or whether you are facing customer churn. Based on the detected intentions, you can take appropriate actions to ensure the growth of your business and minimize customer churn. Intent analysis is supported only for the English language.

For more information, see Intent analysis and filtering.

Support for round icons in Android 7.1 mobile apps

To improve the look and feel of Android mobile apps, round icons are now supported in apps that are created for Android 7.1. You can add the icons to the assets.zip file during the customization stage when you build the app in the Pega^® Platform.

For more information, see Branding mobile apps.

Decision Analytics portal replaces Predictive Analytics Director portal

The Decision Analytics portal replaces the Predictive Analytics Director (PAD) portal, the Text Analytics landing page, and the Adaptive Models Reporting landing page. In this new work area for predictive analytics and text analytics, the business scientist can control the full model life cycle by building predictive models, importing PMML models, building sentiment analysis and text classification models, creating and monitoring adaptive models, and updating any existing models.

For more information, see Overview of the Decision Analytics work area.

Remotely start automation server jobs to perform branch operations

You can remotely start a job on your automation server, such as Jenkins, after an activity has occurred, for example, after you push a branch to a remote system of record. You can configure a continuous delivery pipeline on the job by using the branches REST service and merges REST service to detect conflicts, merge branches, and return the status of the merge. By remotely starting a job to detect conflicts and merge branches, you can more quickly deliver higher-quality software.

For more information, see the following PDN articles:

• Using branches with Pega repositories in a continuous integration and development pipeline.
• Remotely starting automation jobs to perform branch operations and run PegaUnit tests.
• Performing branch operations in a continuous integration and delivery pipeline with REST services.

Node classification

By using the node classification feature, which segregates nodes by their purpose, you can now configure one node with multiple node types. When you start a node with multiple node types, the node runs a set of agents and listeners that are associated with the specified node types. From the Node Classification landing page, you can view and configure the agents associated with node types, view listeners associated with node types, and open Agent rule forms, agent schedules, and Listener rule forms.

For more information, see Node Classification, Configuring node types for agents and listener and Node classification.

Ability to persist request data for synchronous REST Service failures

Request data can now be persisted when synchronous REST Service processing fails. To ensure that data is not lost and can be reprocessed, set the Execution Mode on the rule form to Execute synchronously (queue on error).

For more information see Service REST form - Completing the Service tab.