Published Release Notes

Automated Unit Testing is unavailable

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

Users with custom roles defined must add the pxUpdateRecents privilege to see work in the Recent Items Explorer. 

Use standard Developer portal

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

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

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

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.

Use multiple built-on applications to enhance ruleset reuse

Applications can now have multiple built-on applications, allowing rules to be reused as a part of a built-on application at run time while being developed independently at design time.

Previously, applications built in Pega 7.1 and earlier versions were assembled in a single linear application stack--one application built on top of another application, and so on. Attempting to reuse rulesets and frameworks across applications resulted in having to splice applications together, creating challenges when attempting to support the use of these custom created applications. Starting in Pega 7.2, applications are built on to other applications by using a hierarchical tree structure, and the Pega 7 Platform automatically converts this tree into a linear application stack.

For more information, see Using multiple built-on applications and the Ruleset behavior at design time section in Application stack hierarchy for multiple built-on applications.

Support for delegating map values, correspondence rules, and circumstances

You can now delegate map values and correspondence rules from the Actions > Delegate menu. In addition, you can delegate circumstanced types of the following supported rules and data types:

• Map values
• Correspondence rules
• Paragraphs
• Decision tables
• Data types

Offline support for mobile applications

You can work on assignments and create cases while your mobile device is offline. By enabling offline support for a case type, you can move cases closer to resolution while your application is disconnected from the network.

For more information, see Enabling offline for support for a case type.

Relevant records to define reusable assets

Relevant records describe the collection of rules that refine the behavior, presentation, and definition of a case or data type. They are commonly used to designate records from an inherited class as important or reusable in a child class.

Use relevant records to define information displayed in certain Pega 7 Platform application screens and fields. The Pega 7 Platform provides a number of items marked as relevant records, and you can further manage relevant records for your own case and data types.

For more information, see Relevant records.