Published Release Notes

Automatically populate columns on import

If an imported archive file adds columns to existing tables, Pega Platform ™ can automatically expose and populate the new columns during the import. For more information, see Import wizard.

Support for OAuth 2.0 authorization code grant type

Pega Platform™ now supports the OAuth 2.0 authorization code grant type, which allows Pega Platform to act as an OAuth 2.0 access token provider for native applications on mobile and other devices. By using the authorization code grant type for mobile clients, you no longer need to implement a variety of standards for various authentication providers. The authorization code grant type also supports the Proof Key for Code Exchange standard (PKCE) for securing public clients.

For more information, see Creating and configuring an OAuth 2.0 client registration.

Automatically revalidate and save classes after upgrade

To automatically revalidate and save classes after an upgrade, edit the product rule definition. After you upgrade the application, the classes you specify are revalidated and saved under the application version context you provide. If the application version exists on the target system before the upgrade, the revalidate and save process is not called.

For more information about editing the product rule, see Specifying product rule deployment options.

Multi-answer questions available for surveys

Pega Platform™ now supports multi-answer questions for all types of surveys. You can use multi-answer questions to collect multiple answers from users. For example, you can ask users to list all the languages that they speak by selecting multiple check boxes.

For more information, see Designing a survey.

View status of custom search indexes

Custom search indexes are special purpose indexes that are created and managed outside of Pega Platform™. You can view the status of custom search indexes on the Search landing page to see whether they are complete. This information is useful for troubleshooting and can help you determine whether to rebuild the index.

For more information, see Checking search index status.

Enabling access to upgraded help

After upgrading to Pega Platform ™ 8.1, the default URL to the upgraded help files might be incorrect. To enable access to the latest help files, reset the URL:

1. In the header of Dev Studio, click Configure > System > Settings > URLs.
2. Enter the Online Help URL:

   https://community.pega.com/sites/default/files/help_v81/

3. Click Save.
4. Log out and log back into Pega Platform.

New Email Manager portal

From the Email Manager portal you can more easily and quickly triage received emails and create business cases in a Pega Platform™ application. You can use the Email Manager portal with an application that is used with Intelligent Virtual Assistant for Email. The Email Manager portal suggests business cases for you to create from emails and automatically sends replies to a customer.

For more information, see Email Manager portal.

@java and locatable pages no longer supported

@java and locatable pages are no longer supported. Existing rules that use @java and locatable pages will continue to work; however, changes to these rules cannot be saved unless @java and locatable pages are replaced by supported functionality. Use a rule utility function (RUF) instead of an @java page, and use a data page instead of a locatable page. In addition, Pega Platform™ displays a guardrail warning when you open a rule that uses an @java page or a locatable page.

Log Management adds log categories

Pega Platform™ provides default log categories, but now you can also create custom log categories. You can associate loggers with a defined category according to your criteria and you can select the log level for all loggers in that category. The log level determines the type and severity of messages that are included in the log file. For example, you can choose to show all log messages or only the most severe.

For more information, see Log categories and Log levels for log categories.

Use repositories as sources for File data sets

You can configure remote repositories, such as Amazon S3 or JFrog Artifactory, or a local repository, as data sources for File data sets. By referencing an external repository from a File data set, you enable a parallel load from multiple CSV or JSON files, which removes the need for a relational database for transferring data to Pega Platform™ in the cloud.

For more information, see Creating a File data set record for files on repositories and Configuring a remote repository as a source for a File data set.