Published Release Notes

SAML configuration supports global resource settings

In the SAML Authentication Service form, you can now use global resource settings, which allow greater flexibility for values that change compared to using fixed text values. Apply global resource settings, which are dynamic values, in the Identity Provider (IdP) information section and the Service Provider (SP) settings section of the form.

For more information, see Authentication Service form - Completing the SAML 2.0 tab.

Fingerprint authentication in Pega Mobile Client

The authentication feature in Pega Mobile Client has been extended to support user credentials that are secured by a fingerprint reader. The FingerprintAuthenticator object and its methods replace the TouchID API. A compatibility layer has been created to support custom mobile apps that use the deprecated API. This functionality is available on iOS and selected Android devices.

For more information, see Authentication API.

Restrict visibility of scalar property values for certain users

You can use the Access Control Policy rule to mask individual scalar property values from specified users. You can restrict visibility for the following property types:

• DateTime
• Integer
• Text

For more information, see Masking property visibility for users.

New System Queue Management landing page

You can manage your system queues from the new System Queue Management landing page. You can use this landing page to quickly and efficiently debug applications without exiting Designer Studio. In addition to viewing items in a queue, you can defer, remove, and requeue items in a queue, stop items in progress, and view an item's XML.

As a result of this enhancement, the Broken Queue landing page has been removed.

For more information, see System Queue Management landing page.

Enhancement to the error and warning handling JavaScript API

During offline post processing of a flow in an application, you can now use the ClientCache JavaScript API to handle informational and warning messages in addition to error messages. Several ClientCache API JavaScript functions have been updated for this purpose. Informational, warning, and error messages are displayed when you submit a form, but only error messages prevent you from advancing the case.

For more information, refer to Error and warning handling API in offline mode.

Enable and disable functionality with feature toggles

You can enable and disable functionality in your application for development and testing by creating feature toggles on the Toggle Management landing page. You can also manage the toggles in your application from the landing page. For example, you can review the toggles that you want to retire at the end of a release, or migrate a toggle to other applications by changing the associated ruleset.

For more information, see Creating a toggle.

New customization options for paused custom mobile apps on Android

You can now customize the presentation of a paused custom mobile app for Android. You can upload a custom status bar icon and customize the title and message that are displayed in the device's notification area. Also, you can use a new optional parameter of the startKeepAlive method of the Pega Mobile Client's Container API as an alternative way of setting the notification title.

For more information, see Customizing the paused Android app notification.

Consistent authoring experience for sections

Section references inside a dynamic layout have the same configuration options as a top-level section within a section (section include). Section references reduce the need for included sections, reduce the size of the document object model (DOM), and provide a more consistent authoring experience. You can specify a container format, set view and update privileges, and defer content load for sections within or outside of a dynamic layout. For more information see Harness and Section forms - Adding a section.

Data encryption across search nodes

You can now encrypt communication among search nodes. Encryption secures the data that is transferred across nodes so that it cannot be accessed by unauthorized hosts. Encryption is enabled by default for new installations and upgrades from Pega^® 7.1.6 or earlier to Pega 7.3. Encryption is not enabled by default for upgrades from Pega 7.1.7 or later to Pega 7.3. You can enable and disable search encryption from the Search landing page or by using the indexing/distributed/enable_inter_node_encryption Dynamic System Setting.

For more information, see Enabling and disabling encryption for communication among search nodes.

Support for following users in the Pega Express and Case Manager portals

You can now follow users in both the Pega Express and Case Manager portals. Posts that are made by users whom you are following are displayed in your Pulse activity feed in your dashboard. In addition, an icon indicates whether followed users are online.

For more information, see the following help topics:

• Following a user (Pega 7.3)
• Following a user (Pega 7.3 express)