Published Release Notes

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.

Support for additional health metrics on the Application Quality landing page

On the Application Quality landing page, you can monitor the health of your current application to identify areas that need improvement before deployment. The landing page provides application metrics such as the number of executable rules, the guardrail score, the number of guardrail warnings, the test coverage percentage, and the pass rate of PegaUnit tests. From this landing page, you can also view data for the entire application, for each of its cases, and for rules that are not part of any case type.

For more information, see Application Quality landing page.

Automatic draft off mode for processes in case types

App Studio now supports automatically turning off the draft mode for processes in your case types. Any process that you add to a case type is in draft mode by default so that you can run the case type to check the run-time behavior even if the process contains errors. However, in a production environment, processes in draft mode do not work. To save time and deliver your projects faster, any process that has no errors now automatically switches off draft mode when you save the case type. Additionally, Case Designer now displays a list of errors that processes in your case type include, so that you can quickly locate any issues.

For more information, see Save time and effort with automatic draft off mode for processes in case types (8.5), Draft mode of case processes.

Custom properties can be passed to an Oracle database

You can pass a customizable set of property values to an Oracle database when a connection is established so that an SQL statement can be run. This feature provides the ability to implement object-level security for data access from a Pega 7 Platform application by defining Virtual Private Databases (VPDs) on class tables that reference the information passed. For example, you could pass in an operator's branch office into the context of every query run against the Oracle database to ensure that the operator has access only to data that is applicable to the operator's branch.

This feature is available only for Oracle databases and for a Data-Admin-DB-Name instance that is not PegaRULES or PegaDATA, and has the same connection metadata (JNDI, URL) as PegaData.

See Passing custom properties to an Oracle database.

Privilege inheritance support through access roles

Privilege inheritance simplifies the process of defining privileges that are relevant in multiple classes. When determining whether a user should be granted a named privilege that allows a type of access to a class, Pega^® Platform searches for Access of Role to Object (Rule-Access-Role-Obj) rules that are relevant to the target class and to the access roles listed in the user's access group, and considers the privileges granted or denied in those rules. When privilege inheritance is enabled within an access role, the search for relevant Access of Role to Object rules begins with the target class and, if necessary, continues up the class hierarchy until a relevant rule is found.

For more information, see Privilege inheritance for access roles.

Package caching is not supported in offline-enabled applications built with the UI Kit 7 (09-01-01) portal

When you create an offline-enabled application in Pega^® Platform, by default, it uses a portal with the UI Kit 7 (09-01-01) ruleset. In such a case, the package caching functionality cannot be used. You must either disable caching on the Advanced tab of the Access Group rule form, in the Offline Configuration section, or use an adaptive design instead of rendering different elements for different devices with the UI Kit 7 (09-01-01) ruleset.

For more information, see Access Group form - Completing the Advanced tab.

Create simple URLs for work objects

You can now represent your work objects with simple URLs by using the new URL Mappings rule. Simple URLs are meaningful and easy to share with others, and improve collaboration between users of the same Pega^® Platform application. You can define different URL patterns to use in your application for your work objects (cases), reports, landing pages, or others. You can also generate canonical URLs for your case types to make all instances of these case types searchable by third-party search engines. To enable search engine indexing, a link tag is added to your case object harness.

For more information, see URL Mappings.

Enhanced adaptive model reporting

The new Model report replaces the Behavior and the Performance overview reports to improve report usability and provide consistent information. You can export your Model reports into PDF or Excel files to view or share them outside the Pega® Platform. The Model report also includes information on the groups of correlated predictors where the best performing predictor from each group is active in the model and other remain inactive; this information helps you understand why predictors are active or inactive.

For more information, see Generating a model report.

Manage propositions in multitenant environments

Proposition Management is now supported in multitenant environments of Pega® Platform. The DisablePropCache Dynamic System Setting switches off the use of a proposition cache. When you import propositions in strategies, you can import only versioned propositions (Decision Data rules). Unversioned propositions are not supported under this setting, but these can be converted to versioned propositions.

For more information, see Unversioned propositions, Synchronization of the proposition cache, and Converting groups with unversioned propositions.

Enhanced reliability and stability of scenario tests

Several enhancements have been made to scenario tests to increase their stability and reliability. With enhanced improvements, you can now:

• Delay the execution of a step within a scenario test to add latency to a web browser and actions on a web page. This prevents tests from failing when a dynamic web page does not load all page element at once, but the test finds page elements that are immediately rendered.
• Automatically rerun failed scenario tests, which might fail because there are temporal stability issues on the environment or because the application UI is slowly renders.
• View the run history of scenario tests so that you can analyze the history of a test over time.

For more information, see the following:

• Delay the execution of a step within a test and rerun failed scenario tests for enhanced scenario test stability (8.5)
• Changing application quality metrics
• Automatically rerunning failed scenario tests
• Creating scenario tests