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.
Security fields in JFrog Artifactory repository rule form removed
Valid from Pega Version 8.1
The fields in the Security section of the JFrog Artifactory repository rule form, including the Secure protocol field, the Truststore field, and the Keystore field, were not functional in Pega Platform™ 7.3, 7.3.1, and 7.4. This section has been removed from the JFrog Artifactory repository rule form in Pega Platform 8.1.
DCO Compatibility tool is deprecated
Valid from Pega Version 8.1
The DCO Compatibility tool has been deprecated. Use the Application Guardrails landing page to see the compliance score and any warnings for your application.
For more information, see Application Guardrails landing page.
Identify team members working on a rule
Valid from Pega Version 8.1
By using the team collaboration widget, you can see who on your development team is working on the rule that you are viewing. This widget is displayed in the section header when you are using the Case Designer, Data Designer, or Channels and interfaces configuration pages. When you update a page, a notification is sent to other collaborators stating that the content has been updated and prompting them to refresh to see the latest content.
Troubleshooting offline-enabled applications in a browser
Valid from Pega Version 8.1
You can now troubleshoot offline-enabled applications by using the Tracer tool and developer tools that are available in a web browser. You can troubleshoot scripts that are running when the application is running, without having to use additional debugging tools.
For more information, see Application debugging using the Tracer tool, Troubleshooting offline-enabled applications with the Tracer tool in a browser, and Offline capability.