Published Release Notes

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.

Service REST monitoring

You can now monitor response and request data for REST services and view the results in Pega^® Platform. The ability to monitor REST services is useful for debugging your application during development, for example, when a request fails. It is not recommended that you monitor REST services in production environments because monitoring might affect performance and depending on the number of incoming service requests, there is a chance that over a period of time, the invocation history might get large enough so that you run out of database space. You can configure monitoring globally for all of your REST services by using the service/EnableglobalMonitoring Dynamic System Setting with owning ruleset Pega-IntegrationEngine, or by using the service package and service rule forms.

For more information, see Service REST monitoring.

Attach Content control enhancements

You can now use the Attach Content control in Pega^® Platform to configure compression options that limit the size of files created on a mobile device. For example, you can choose from predefined settings to limit video duration or image size. These settings apply when the user records a new video or takes a new photo, but they do not apply to prerecorded media.

Also, when attaching content to a custom mobile app, users can now select any type of file from any source that is available in the device's native file picker component.

For more information, see Configuring file size options for the Attach content control.

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.

Build predictive models with the genetic algorithm

A genetic algorithm solves optimization problems by creating a generation of possible solutions to the problem. In Pega^® Platform you can utilize the functionality of genetic algorithms by using the genetic algorithm model in the Analytics Center portal. With this type of predictive model, you can create highly predictive, non-linear models by selecting the best performing model from the last generation.

For more information, see Creating models and Creating a genetic algorithm model.

Internet Explorer 11 support

7.1.5 now provides support for Internet Explorer 11 (IE11). For those customers interested in information about IE11 support in previous releases, refer to the Platform Support Guide.

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.

Apply logic to data import fields

When importing data from an external system, you can translate data fields into values that can be read by Pega^® Platform. From the Import wizard, you can do the following actions:

• Apply a decision tree or decision table to the data that is imported for a field.
• Use imported data for a field to look up a value in another record. For example, you can look up the key of a record that uses an external identifier to populate a foreign key field.
• Create templates that contain business logic, which eliminates the need to handle data transformations manually during preprocessing.

For more information, see Transforming data during import.

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.

New alert for distinct values query

The PEGA0093 alert identifies performance issues when a distinct values query from virtual reports or the getDistinctValuesForProperty API take longer than the threshold. For more information, see PEGA0093: Distinct values query took more than the threshold.