Published Release Notes

Data page unit test case setup and cleanup

You can now use one or more data pages, data transforms, or activities to set up a clipboard page with the appropriate properties before you run a data page unit test case. You can also use activities to create any required test data, such as work or data objects.

After you run a data page unit test case, the data pages that were used to set up the test environment are automatically removed. You can now also apply additional data transforms or activities to clean up the clipboard.

For more information, see Setup and cleanup of data page unit test cases.

New assertions for data page unit test cases

You can now configure the following assertions for data page unit test cases:

• Result count assertions for page lists, page groups, value lists, and value groups
• Unordered list and ordered list assertions for page lists

The Pega 7 Platform now supports these assertions in addition to expected run-time assertions for the data page and property assertions for any property type.

For more information, see Data page unit test case assertions.

Unicode-enabled database for international language support

The Pega 7 Platform database has been enhanced to natively support Unicode multibyte character set encoding when using Postgres on Pega Cloud. This enhancement allows you to store data in languages such as Japanese, Chinese, and Korean.

Change the type of an existing field

You can now change the type of an existing field on the Data model tab of a case type or data type, resulting in a more efficient development process at design time. If there are any validation issues when changing a type, an error message is displayed, and the type cannot be modified by using this method.

For more information, see:

• Modifying the type of a field
• Troubleshooting validation errors when changing the type of an existing field

Open authoring for rule forms has been removed

Open authoring for rule forms has been removed. You can now edit decision tables and map values by using the application and supported browser of your choice; Microsoft ActiveX controls are no longer required. In addition, support for external XML, HTML, and Java IDE editors has been removed.

Execute Tests service to run all data page unit test cases

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.

Pega Express application views simplify portal creation

Pega Express application views offer a simple, intuitive authoring experience for portals. Application view templates support responsive application development and offer mobile-specific templates. You can create portals by selecting from a predefined set of application view templates.

For more information, see Application views.

Rule form search

You can now search for content within some rule forms by clicking Search rule on the Actions menu. The search results and the tabs of the rule form that contain the search results are highlighted.

For example, you can find the properties that are used in a when condition inside an activity without navigating to each tab, when condition, transition, and method in the activity.

Delegate service-level agreements

You can now delegate service-level agreements (SLAs) to your business line by clicking Actions > Delegate. You can also delegate circumstanced versions of SLAs.

For more information about delegations, see Delegating a rule or data type.

Circumstance a rule by different properties

You can specialize or circumstance a rule by a different property even if the base rule is circumstanced by another property. This flexibility can help address cases where the same rule needs to be circumstanced by different properties. When you circumstance a rule by different properties, the circumstanced versions of the rule must be in different rulesets or Applies To classes.

You can circumstance a rule by a different property in the same ruleset, but in a higher version, by withdrawing the existing circumstanced versions.

For more information, see Circumstance a rule with different properties or templates.