Improve cluster security by limiting concurrent operator sessions
Valid from Pega Version 7.3
You can increase the security of a Pega® Platform cluster by limiting the number of concurrent sessions allowed for each operator. Because operators typically do not require multiple concurrent sessions for performing their work, limiting the number of sessions reduces the chance that an unknown or untrusted person could access systems in the cluster. Use the new setting Number of concurrent sessions allowed for each operator on the Production tab of the System Data Instance form to configure the number of concurrent sessions for operators. You must restart your system when you change this setting. You can also create a list of operators by using the presence/maxsessions/operators/whitelist Dynamic System Setting, to which the maximum number of concurrent sessions setting will not apply.
For more information, see System form - Completing the Production tab.
Logging service now uses Apache Log4j 2
Valid from Pega Version 7.3
The Pega® Platform now uses the Apache Log4j 2 logging service. Apache Log4j 2 improves performance and provides support for all log file appender types. As a result of this upgrade, the prlogging.xml file has been renamed to prlog4j2.xml and the format of the file has changed considerably.
For details about the new file format see Pega Platform logging with the Log4j 2 logging service.
For new installations or for upgrades to systems that were using the default logging configuration, no changes are needed. For information about updating custom log files after upgrading, see Customizations to the prlogging.xml file must be manually ported after upgrade. For information about updating your socket server if you use remote logging, see Socket server has changed for remote logging. For information about updated the web.xml file after upgrading, see Log file description in web.xml incorrect after upgrade to Apache Log4j2.
Create connections to repositories
Valid from Pega Version 7.3
Pega® Platform can communicate with common repository technologies. Whenever an action creates a RAP, Pega Platform can browse, publish, or fetch artifacts: for example, when exporting an application, product, branch, or component. Repositories are instances of the Data-Repository class which holds all necessary connection information.
Pega Platform includes tools to connect with the following repository types:
- JFrog Artifactory
- Amazon S3
For more information, see Creating a JFrog Artifactory or Amazon S3 repository connection.
Delegation experience in revision management
Valid from Pega Version 7.3
Revision managers can now control rule authoring by assigning a delegation experience to any rule that is part of a revision management change request. Delegation experience types offer different rule authoring capabilities, so the revision manager can select the appropriate delegation experience for the task and the strategy designer’s experience.
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.