Published Release Notes

End of support for form-based rule forms in Pega 7.1.9

Rule forms that are configured to render as forms are no longer supported in Designer Studio or end-user applications. Form-based configurations are found on custom rule types that were created in earlier versions of Pega 7 and are characterized by pop-up windows that are rendered externally from Designer Studio.

Reconfigure Pega 7 applications that use such rule forms by using standard harnesses and sections.

1. Open the class form.
2. Click the Advanced tab.
3. Select Harness from the Rule formmenu.
4. Create a new harness and new sections that implement the logic of the custom rule, using standard user interface layouts and controls.

Migrating custom rule forms to harnesses and sections offers the following benefits:

• User interfaces become HTML5 WC3 compatible and responsive to different screen sizes.
• User interfaces become cross-browser compatible, rendered consistently in Google Chrome, Mozilla Firefox, Apple Safari, and recent versions of Microsoft Internet Explorer.
• Rendering performance on modern browsers is dramatically improved.
• User interface pop-up behavior is eliminated; all windows are rendered inside Designer Studio and end-user applications.

Pega 7 Express is available on-premises

You can now experience Pega 7 Express by switching your enterprise application from Designer Studio to express mode. By default, users with access to the Developer portal can switch between these two development environments. You can also create an express application to work in express mode exclusively.

Trial versions of Pega 7 Express continue to be available on the cloud. To view the documentation for both the cloud and on-premises environments, see Getting started with Pega 7 Express.

Access to Pega 7 Express from within Designer Studio is not supported on mobile devices.

Context-specific documentation is not available in express mode

Help topics that are opened from express mode display content that is specific to Designer Studio.

If your system is dedicated to applications that are developed in express mode exclusively, and you do not need Designer Studio help topics, you can set the Online Help URL field on the System Settings landing page to: https://pdn.pega.com/sites/default/files/help_p7e/procomhelpmain.htm. Alternatively, you can view the contextual help system for Pega 7 Express in a separate browser tab.

Design-time limitations in express mode

Some limitations apply when you develop an enterprise application in express mode. At design time, some features are disabled or have limited options when you configure them in Designer Studio and switch to express mode. The use of these features does not restrict the run-time behavior of your application; however, you cannot change the configuration of these features unless you switch from express mode to Designer Studio.

For more information about each limitation and the recommended action to take, see the following information:

• Pega 7.2.2 Design-time limitations in express mode
• Pega 7.2.1 Design-time limitations in express mode
• Pega 7.2 Design-time limitations in express mode
• Pega 7.1.9 Design-time limitations in express mode

Support for rule rebasing

You can now rebase the rules on your development server with the most recently committed rules from a centralized system of record (SOR). For example, after rules are merged on the SOR, you can rebase your development application to refresh your application with the merged rules. Development teams working in two separate development environments can share their changes, keep their local rulebases synchronized, and reduce the probability of conflicts with other development teams.

For more information, see Rule rebasing.

Add new commands in the Facebook channel preview console

Now you can not only edit existing commands in the preview console for a Facebook channel but also add new command responses and associate them with intents. For example, you can add a new response command in the preview console in a case in which you entered a command and no response was found for the generated intent. This functionality gives you more control over the Facebook channel configuration and makes the preview console easier to use.

For more information, see Simulating a chatbot conversation.

Enhancements to PegaUnit test cases and test suites

Several enhancements have been made to PegaUnit test cases and test suites.

• You can now use advanced filters on the Automated Testing landing page and when you add test cases to a test suite to search for information.
• After you run a test case on the Edit Test Case form or a test suite on the Edit Test Suite form, the header now displays the expected and actual run-time values.
• You must now specify at least one assertion before you can save a test case.
• You can now compare a property to multiple values so that the assertion passes if any property meets the defined criteria.
• You can now use the is greater than and is less than comparators for date and date-time properties.

For more information about PegaUnit testing, see PegaUnit testing.

Execute Tests service now supports application name as a parameter

You can now use the application name and version as a parameter when running the Execute Tests service (REST API). When you build an application on Pega® Platform in a continuous delivery pipeline, you can use the Execute Tests service to validate the quality of the build by running PegaUnit test cases that are configured for the application.

For more information about the service, see Running PegaUnit test cases and test suites with the Execute Tests service in Pega 7.3.1.

Monitor application health on the Application Quality landing page

On the Application Quality landing page, you can view various quality-related data in one place so that you can monitor the quality of your application and correct any issues. The Application Quality landing page contains a summary of guardrails compliance, PegaUnit test coverage, and results of PegaUnit tests.

For more information, see Application Quality landing page.

View PegaUnit test reports

The Reports tab on the Automated Testing landing page contains tables and charts that display the percentage of rules on which PegaUnit test cases are configured, and the results of PegaUnit test execution. By looking at the data on this tab, you can see which tests failed and investigate them.

For more information, see Viewing PegaUnit reports.