Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Add the security checklist to applications created before 7.3.1

Valid from Pega Version 7.3.1

The security checklist is now automatically added to applications. You can manually add the security checklist to applications that were created in earlier versions.

You can improve the security of your application by completing the tasks on the checklist.

The following task reflects the procedure on how to manually add the security checklists to Designer Studio prior to 7.3.1:

  1. In the header of Designer Studio, click the name of the application, and then click Definition.
  2. Click the Documentation tab.
  3. In the Application guides section, click Add guide.
  4. In the Application guide& field, enter pxApplicationSecurityChecklist.
  5. Click the Configure icon in the Available in column and select the portals (App Studio and Dev Studio) that you want to add the security checklist to.
  6. Click Save.

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.

Authenticate REST data sources by using OAuth 2.0

Valid from Pega Version 7.2.2

You can now authenticate the data sources that are created from your REST integration by configuring OAuth 2.0 authentication in the New REST Integration wizard. You can specify or create an OAuth 2.0 authentication profile in the wizard by using the client credentials or authorization code grant type.

For more information, see OAuth 2.0 in REST integration.

New hashing algorithm for Password property types

Valid from Pega Version 7.2.2

To provide extra protection against brute-force attacks, a new hashing algorithm has been added to the Pega 7 Platform. Bcrypt is used as a default hashing algorithm for Password property types. The bcrypt key setup algorithm takes a long time to process. This means that potential attackers would have to spend a substantial amount of time testing every possible key.

For more information, see Using the bcrypt hashing algorithm for Password property types.

Discovery features for access control policies

Valid from Pega Version 7.2.2

Access control policies now support discovery features that allow end users to view limited, customizable information about class instances that fail Read policies but satisfy Discover policies. Two types of Discovery gadgets are provided, and when discovery features are enabled, a Discovery gadget is included in the Report Viewer and in search results. Developers can customize these gadgets and include them in other parts of an application user interface.

For more information, see Discovery features for access control policies.

Update and delete actions available in access control policies

Valid from Pega Version 7.2.2

Access control policies support update and delete actions on objects. These actions control which specific instances of a class can be created, updated, or deleted by an end user in a case.

For more information, see Creating an access control policy.

Customized data imports

Valid from Pega Version 7.2.2

You can now further customize the data import process in Data Designer by:

  • Setting a default import purpose and preventing the selection of an import purpose to speed up frequent imports of the same kind
  • Removing the import purposes that you do not need for your data type
  • Defining a default field mapping between the fields in the .csv file and the fields in your data type that act as a unique identifier (key), to save time during the import process
  • Skipping the import progress screen and showing progress contextually within your application
  • Including the link for data import anywhere in your application or calling it in the background from a service or agent

For more information, see Data import customization.

Enhanced data imports

Valid from Pega Version 7.2.2

The data import process in Data Designer has been enhanced to give you more options. You can now import case types, save and use templates for field mapping, add data without updating existing data, specify date and time formats, and reprocess erroneous records by downloading a .csv file that lists the errors in your data import. You can also adjust the data import wizard to the context where it is included.

For more information, see Data import enhancements

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us