Fingerprint authentication in Pega Mobile Client
Valid from Pega Version 7.3
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
Valid from Pega Version 7.3
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.
Enhancement to the error and warning handling JavaScript API
Valid from Pega Version 7.3
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.
New customization options for paused custom mobile apps on Android
Valid from Pega Version 7.3
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.
Disable inactive operators
Valid from Pega Version 7.3
As a system administrator, you can control access to an application by disabling Operator IDs. To disable an Operator ID, you can use one of the following options in Designer Studio:
- Call the Service REST: user.
- Change settings on the Operator Access tab on the System Settings landing page or on the Security tab on the Operator ID form.
- Define the number of inactive days in the security policies before an Operator ID is automatically disabled.
For more information, see System Settings - Operator Access tab, Enabling Security Policies, Security tab on the Operator ID form.
Security landing pages and features require privileges
Valid from Pega Version 7.3
Security-related landing pages and features are no longer visible and accessible to every user. To view and configure the following security features, you must have the appropriate privileges:
- Attribute-based access control (ABAC) policies require the pzCanManageSecurityPolicies privilege.
- The Authentication Services landing page requires the pzCanCreateAuthService privilege.
Authenticate users in processes with a JSON Web Token
Valid from Pega Version 7.3
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.
Support for round icons in Android 7.1 mobile apps
Valid from Pega Version 7.3
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.
Property-level security for full-text search
Valid from Pega Version 7.3
Property-level security has been added to full-text search so that you can limit access to sensitive data. From the Search landing page, you can specify whether to include properties with access control policies in search results. In addition, for custom search, you can select which properties to include in full-text search by selecting options on the Search landing page and Custom Search properties instance.
For more information, see Specifying custom search properties and Excluding properties with access control policies from search results.
Today widget for iOS custom mobile apps
Valid from Pega Version 7.3
The Pega Mobile Client has been extended to support a Today widget in custom mobile apps for iOS. By default, the Today widget displays the current user's list of work objects. This functionality is available only for offline-enabled custom mobile apps and requires that your certificate set include a widget provisioning file.
For more information, see Configuring a Today widget on iOS.