Published Release Notes

Security fields in JFrog Artifactory repository rule form removed

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

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

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

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.

@java and locatable pages no longer supported

@java and locatable pages are no longer supported. Existing rules that use @java and locatable pages will continue to work; however, changes to these rules cannot be saved unless @java and locatable pages are replaced by supported functionality. Use a rule utility function (RUF) instead of an @java page, and use a data page instead of a locatable page. In addition, Pega Platform™ displays a guardrail warning when you open a rule that uses an @java page or a locatable page.

Test ID added to repeating dynamic layouts

A unique Test ID property has been added to repeating dynamic layouts to support automated testing, enabling you to write dependable automated tests against any Pega application. By including this unique identifier in your automated testing, you ensure a higher level of productivity and reliability within your applications.

For more information, see Test ID and Tour ID for unique identification of UI elements.

Relevant records management shows more information

Relevant records for a class now include more information that you can use to manage the records for your application development. As a result of these enhancements, you can:

• View inherited and inactive relevant records for the specified class.
• Mark specific records as active or inactive for the specified class.
• Mark specific records as relevant on the rule form.

You can use these new details to filter the list of relevant records for a class on the Relevant Records tab of the selected class. For more information, see Managing relevant records and Marking records as relevant records.

Autogenerated controls have unique IDs

Autogenerated controls have a unique ID by default. This unique ID ensures that the Document Object Model (DOM) is HTML5-compliant and avoids problems that can be caused by elements having the same ID. The setting to enable or disable unique IDs is on the HTML5 Application Readiness page.

For more information, see Unique IDs in autogenerated controls.

New themes in App Studio

New themes in App Studio determine the default colors for elements in your user interface, such as buttons and links, as well as your typography. By selecting a theme in App Studio, you can quickly apply a consistent style to your application and save development time by not having to edit the application skin in Dev Studio.

For more information, see Changing your theme.

Select or edit a label format at run time

At run time in App Studio, when you edit a control, you can now select a new label format for the control or edit the currently selected label format. This change provides you with the flexibility to update control labels in real time as you process cases.

For more information, see Styling controls at run time.