Published Release Notes

REST services support password credentials and JWT Bearer grant types

Pega^® Platform REST services now support password credentials and the JWT (JSON Web Token) Bearer grant type when you enable OAuth 2.0-based authentication. By using password credentials, you can quickly migrate clients from direct authentication schemes, provide additional flexibility when other grants are not available, and integrate your application with REST services in other applications. You can add compatibility with modern JWT-based cloud security IDPs by using the JWT Bearer grant type.

For more information, see About OAuth 2.0 Provider data instances, OAuth 2.0 Client Registration data instances - Completing the Client Information tab, Creating an Identity Mapping data instance.

Mobile optimized grid enhancements

Grid (table) layouts optimized for mobile support conditional visibility layout, row, and cell content. You can configure visibility as a client-run expression for use offline, or use a when rule or server-run expressions for desktop and mobile applications. Conditional visibility allows applications to use the template-based rendering. The UI Gallery includes an example of such a grid.

For more information see Optimize grid layouts for mobile.

Specify a model transparency policy for predictive models

Specify a model transparency policy in Pega^® Platform to indicate predictive models that are compliant or non-compliant to use in particular business issues. Increase the transparency threshold of particular business issues to allow the use of more transparent models. Decrease the transparency threshold to allow for the use of less transparent and opaque models. Models with a transparency score below the transparency threshold are marked as non-compliant.

For more information, see Model transparency for predictive models.

Upgrades and updates from Pega 7.3 on MSSQL fail with column name mismatch

This failure applies only to upgrades and updates from Pega® Platform 7.3 on systems running Microsoft^® SQL Server^®. In Pega 7.3, the capitalization for the column name pc_work_agile.pzPvStream is incorrect. The correct capitalization is pzPVStream. To prevent upgrade and update failures, before you upgrade or update, run the following command from the Microsoft SQL Server Management Studio (SSMS) to rename the column:

EXEC sp_rename ‘data-schema-name.pc_work_agile.pzPvStream', 'pzPVStream', 'COLUMN'

Reports on pc_work_agile table fail in Pega 7.3 on MSSQL

This failure applies only to Pega^® Platform 7.3 on systems running Microsoft SQL Server. In Pega 7.3, the capitalization for the column name pc_work_agile.pzPvStream is incorrect. The correct capitalization is pzPVStream. To prevent reporting failures on the pc_work_agile table, run the following command from the Microsoft SQL Server Management Studio (SSMS) to rename the column after you install Pega 7.3:

EXEC sp_rename ‘data-schema-name.pc_work_agile.pzPvStream', 'pzPVStream', 'COLUMN'

Test when rules by using PegaUnit automated tests

You can now create and run PegaUnit automated tests for when rules. These tests reduce the testing effort required for when rules and improve product quality. They also help to identify issues that might be introduced in new releases by providing quick automated regression testing.

For more information, see Unit testing a when rule.

Use of PegaRULES_Extract_Marker.txt to delete cache is deprecated

The PegaRULES_Extract_Marker.txt file is deprecated. The system uses the presence or absence of the PegaRULES_Extract_Market.txt file to determine at startup whether to delete the static content, service export, and lookup list file system-based caches. In the rare situation that you need to delete these caches manually, use the System Management Application (SMA) ETier Static Content Management page. Using SMA does not require restarting the node.

Define custom dimensions in VBD data sets

Beginning with version 7.3.1, you can define custom dimensions when you create a Visual Business Director (VBD) data set in Pega^® Platform. With this option, you can use any custom or existing property from the Applies To class of the VBD data set as a dimension to visualize your data, in addition to the properties in the default set of dimensions.

For more information, see Creating a Visual Business Director data set record.

Nodes in a cluster do not see each other for Docker, multiple VMs, or multiple NICs setup

If a cluster is set up in Docker, or uses separate virtual machines (VMs) or multiple network interfaces, you must set the public address in the prconfig.xml file for each Pega^® Platform node to avoid problems with node clustering. Add the <env name=”identification/cluster/public/address” value=”IP address”/> setting to specify the public address that is used by each node.

Create simple URLs for work objects

You can now represent your work objects with simple URLs by using the new URL Mappings rule. Simple URLs are meaningful and easy to share with others, and improve collaboration between users of the same Pega^® Platform application. You can define different URL patterns to use in your application for your work objects (cases), reports, landing pages, or others. You can also generate canonical URLs for your case types to make all instances of these case types searchable by third-party search engines. To enable search engine indexing, a link tag is added to your case object harness.

For more information, see URL Mappings.