Monitor standard and custom security events
Valid from Pega Version 7.3
From the new Security Event Configuration landing page, you can select the standard and custom security events that you want the Pega 7 Platform to log automatically for every user session. The security events are grouped into the following types:
- Authentication
- Data access
- Security administration
- Custom
The API logCustomEvent() is provided so that you can create custom security events that are specific to your applications and that can be monitored by the Pega 7 Platform. For more information, see Security Event Configuration.
File data set
Valid from Pega Version 7.3
You can now create a File data set that reads data from a file that is in CSV or JSON format. You can use this type of data set to test data flows and strategies.
For more information, see Creating a File data set record.
Execute Tests service now supports flows, case types, and PegaUnit test suites
Valid from Pega Version 7.3
The Execute Tests service now supports running flows, case types, PegaUnit test suites. Use the Execute Tests service to validate the quality of your builds after every build run.
For more information, see Running PegaUnit test cases and test suites with the Execute Tests service.
Support for creating PegaUnit test suites
Valid from Pega Version 7.3
You can now create PegaUnit test suites to group related PegaUnit test cases and run them in the order that you specify. For example, you can create smoke tests to verify that critical application functionality is working as expected.
For more information, see PegaUnit test suites.
SAML configuration supports global resource settings
Valid from Pega Version 7.3
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
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.
New System Queue Management landing page
Valid from Pega Version 7.3
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
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.
Enable and disable functionality with feature toggles
Valid from Pega Version 7.3
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.