Automated Unit Testing is unavailable
Valid from Pega Version 7.1.1
Automated Unit Testing (AUT) is unavailable in 7.1.1 - 7.1.5.
Starting in 7.1.6, users can access AUT features from supported browser versions of IE.
Privilege required for Recent Explorer
Valid from Pega Version 7.1.1
Users with custom roles defined must add the pxUpdateRecents privilege to see work in the Recent Items Explorer.
Use standard Developer portal
Valid from Pega Version 7.1.1
Customized versions of the Developer portal rely on legacy components and are not supported.
To avoid backwards compatibility issues, update your access group to point to the standard Developer portal prior to upgrade.
Top-level (named) pages may no longer be classless
Valid from Pega Version 7.1.1
Newly created top-level (named) pages may no longer be classless or have a blank pxObjClass property. This change can affect applications upgrading from versions prior to Pega 7 to the latest version, especially when:
- Application logic relies on a blank value in the pxObjClass property.
- An activity assumes a new top-level page is classless and explicitly sets pxObjClass in a Property-Set step.
- A data transform assumes a new top-level page is classless and explicitly sets pxObjClass using a Set action.
To avoid application failures, remove or update any logic that expects a blank pxObjClass. Where possible, use the new engine API that finds a page by both name and class:
findPageWithException(PageName, ClassName);
Activities and data transforms continue to create a top-level page when one does not exist. The class name is now derived from the Pages and Classes tab.
IE8 limits expansion features
Valid from Pega Version 7.1.1
Internet Explorer 8 (IE8) does not support CSS media queries, which are used by re-expansion features in the Designer Studio. IE8 users with low screen resolution (800 x 600) and a small window size may find that the explorer area in the Designer Studio collapses but cannot re-expand.
As a work around, access the Designer Studio from another supported browser version and use the recommended, minimum screen resolution width of 1280 pixels.
All tabs are accessible on delegated rule forms
Valid from Pega Version 7.1.1
Delegates can now access all tabs in a delegated rule form.
You can continue to customize the development experience for delegated users, such as line managers, who may not require the full set of rule form options. For example, you can prevent users from adding new nodes on the Decision Tree form or using the expression builder on the Map Value form. All users, including delegated users, can remove these restrictions if they hold a rule-editing privilege.
For more details on this process and a list of commonly delegated rules, see How to delegate a rule.
Support for rule rebasing
Valid from Pega Version 7.3.1
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
Valid from Pega Version 7.3.1
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
Valid from Pega Version 7.3.1
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
Valid from Pega Version 7.3.1
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.