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.

Unit testing support for more rule types

Valid from Pega Version 8.3

You can now create unit tests for the following additional rule types. You can also create assertions to validate activity status. The expanded rule types for unit testing enable developers to more thoroughly perform regression testing of their application, thereby improving application quality.

  • Collection
  • Declare expression
  • Map value
  • Report definition

For more information about unit testing rules, see Pega unit test cases.

Upgrade impact

With the four new rule types, unit test execution and unit test compliance metrics will change. Reports on automated unit testing of the customer application decrease due to the increased pool of supported rules.

What steps are required to update the application to be compatible with this change?

After a successful upgrade, create Pega unit test cases for the newly supported rules to see updated and accurate unit test metrics.

View application quality metrics by data type

Valid from Pega Version 8.3

You can now view application quality metrics by data type on the Application Quality landing page. The new Data Types tab displays metrics for data types grouped by data objects, which enables you to more quickly understand the overall coverage of the application's integrations and interfaces.

For more information about data type metrics, see Application Quality landing page.

Scenario tests are reusable

Valid from Pega Version 8.3

Existing scenario tests are now reusable in different business scenarios. Before Pega 8.3, you had to create a new test every time a user interface or process flow changed significantly. Now, scenario tests are editable to help you maintain the test stack more effectively.

For more information, see Updating scenario tests.

Java injection vulnerability check

Valid from Pega Version 8.3

Pega Platform™ now notifies you of Java injection vulnerabilities in activities, functions, and stream rules at design time and at run time.  You can customize Pega Platform to check for additional vulnerabilities to ensure that your application runs without problems.

For more information, see Configuring the Java injection check.

Usability improvements to Admin Studio

Valid from Pega Version 8.3

Admin Studio offers a variety of usability enhancements, including:

  • New access groups to differentiate between full and read-only access to Admin Studio
  • A Java class lookup utility
  • A requestor list for the logged-on operator
  • The ability to display system node type in the logs

Also, if your environment uses Predictive Diagnostic Cloud (PDC), the Admin Studio overview page now includes a link to PDC.

For more information, see Managing requestors.

Improvements for automated scenario testing

Valid from Pega Version 8.3

Test automation authors can group related scenario tests into suites. The scenario test suites can be run manually from the Scenario Testing landing page as part of purpose-specific tests such as smoke tests, regression tests, and outcome-based tests. Additionally, automation authors or release managers who monitor tests for an application can disable or quarantine unstable scenario tests so that they do not run.

For more information about creating and managing test suites for scenario testing, see Creating test suites for scenario testing.

Enabling security policies now requires current password

Valid from Pega Version 7.1.3

As part of Pega’s initiative to protect against malicious attacks, the change password dialog has been enhanced.  When Security Policies have been enabled for your system, new users or those with expired passwords will now be prompted for both their existing password as well as their desired new password.

For more details, review the Designer Studio > System > Settings > Security Policies landing page.

Application Express and the Content Security Policy

Valid from Pega Version 7.1.7

Application Express copies (if defined) the Content Security Policy (CSP) name (pyContentSecurityPolicyName) from the built-on application in a new application. It also sets the CSP mode (pyContentSecurityPolicyMode) to report. The values appear in the Content Security area on the application rule's Integration & Security tab.

When checking an application in the DCO Compatibility tool, a warning appears if the CSP name is missing.

Password hashing using SHA-256/SHA-512

Valid from Pega Version 7.1.7

Password hashing using the SHA-256 and SHA-512 hash functions is available for use during the the Pega 7 authentication process with operator, ruleset, and update lock passwords. The SHA-256/SHA-512 hash functions join the previously available MD5 and SHA-1 hash functions.

Using SHA-256/SHA-512 hashing when creating or upgrading a password hash results in increased complexity of the hash, making it extremely difficult and time-consuming to determine hashed password values stored in a database.

Note that once you have updated your system to Pega 7.1.7 and have applied password hashing using the SHA-256/SHA-512 hash functions, reverting back to a previous version of Pega 7 is not advised as this causes hashed passwords using SHA-256/SHA-512 to fail.

See About password hashing for more information.

Token credentials authentication service

Valid from Pega Version 8.3

You can create a new type of authentication service for token credentials authentication, which is useful for offline mobile applications. With token credentials authentication, users need to enter their credentials only once in a session. Subsequent access to the server is authenticated with a token. The token can be generated by the Pega Platform™ authorization layer (OAuth 2.0) or issued by an external identity provider.

For more information, see Configuring a token credentials authentication service.

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