Support for encrypted traffic in a cluster
Valid from Pega Version 7.3
The Pega 7 Platform includes the Ignite platform, which supports encryption for intra-cluster communications. You can now configure encryption for intra-cluster traffic for compliance with regulatory or organizational security requirements.
For more information, see Enabling encrypted traffic between nodes.
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.
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.
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.
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.
Support for following users in the Pega Express and Case Manager portals
Valid from Pega Version 7.3
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:
Enhancements to the Send Email smart shape
Valid from Pega Version 7.3
The following enhancements have been made to the Send Email smart shape:
- You can now configure the Send Email smart shape in Pega Express.
- You can use templates, such as a rejection template, in your email.
- You can use property values, which allow you to insert the value of a field in your case type, such as First Name, within the email.
- You can insert a link to the case ID in your email.
- You can more quickly configure your recipient list by using two options, instead of one, to send messages to either a list of email addresses or to fields.
- You can choose to send either all case attachments in an email, or you can send attachments of a specified attachment category or an attachment type field. You can specify multiple attachment categories and attachment type fields.
For more information, see the following help topics:
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.