Execute Tests service to run all data page unit test cases
Valid from Pega Version 7.2.1
You can now use the Execute Tests service to run a set of tests at the end of build runs. An external validation engine, such as Jenkins, calls the service, which runs all data page unit test cases in your application, and returns the results in XUnit format. Use this service to validate the data in your application and to correct any issues before you deploy your application.
For more information, see Running all data page unit test cases with the Execute Tests service.
Quick and customized data imports
Valid from Pega Version 7.2.1
You can now quickly add, update, or delete data records for your data types by uploading .csv files that contain a large number of records. The bulk import process allows you to import data from a variety of sources and gives you more control over your data. You can customize this process by overriding a data transform to add purposes, a section to add fields, and an activity to define the logic for each purpose.
For more information, see Data import customization.
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.
Enhancements to the REST integration wizard
Valid from Pega Version 7.2.1
You can use the improved REST integration wizard to quickly create data sources in your application. The steps in the wizard are now arranged in a manner that makes the process of creating REST integration more intuitive. You can add custom headers that allow you to connect to complex REST services. You can also enter the name of the system that hosts the REST service, which allows you to group data sources that connect to the same system.
For more information, see the REST integration section in Integration wizards.
Improved security for clipboard pages
Valid from Pega Version 7.2.1
To prevent data leakage and inconsistency, the Pega 7 Platform does not allow properties on a clipboard page to refer to properties on pages with a lower scope. For example, an autopopulate property on a node type clipboard page cannot source data from a data page with scope “requestor” or “thread.”
For more information, see Page scope types for data and declare pages.
Attribute-based access control model
Valid from Pega Version 7.2.1
Attribute-based access control (ABAC) is a security authorization model in which access rights are determined through the use of policies and attributes. A policy decision engine in ABAC evaluates digital policies against available data (attributes) to permit or deny access to the requested resource. For example, you can now determine access rights to cases by examining security attribute values assigned to the user and the case.
For more information, see Attribute-based access control.
Store and source content in Box
Valid from Pega Version 7.2.1
You can now attach content from Box while working on a case in your application. You can attach files directly to your case or include them in a Pulse message. You can also store all the case and Pulse attachments in your application in Box. To enable content sourcing and storage in Box, configure the Content sourcing and Content storage sections on the Integration & security tab of your application rule.
For more information, see Storing and sourcing content in Box.
Show multiple views of data in your application
Valid from Pega Version 7.2.2
You can now show multiple views of data in your application by adding the record editor (pxRecordsEditor) section to a layout, another section, or a cell in a layout. You can configure the section to customize the display and enable the search, import, and export capabilities of the record editor.
For more information, see Multiple views of data in the record editor section.
Support for additional rule types for PegaUnit test cases
Valid from Pega Version 7.2.2
To compare the expected results with the results that are returned by running a rule, you can now create PegaUnit test cases for the following rule types:
- Activities
- Data transforms
- Strategies
- Decision trees
- Decision tables
After you unit test these rules, you can convert them to test cases and configure assertions on the test cases. You can also set up the clipboard with data before tests are run, and clean up the clipboard after tests are run.
For more information, see PegaUnit testing.
Page assertions are supported for PegaUnit test cases
Valid from Pega Version 7.2.2
You can now create page assertions for PegaUnit test cases. Because data transforms and activities can create or remove pages, you can configure page assertions to determine whether a page exists after you run PegaUnit test cases.
For more information, see Configuring page assertions.