Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

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.

@java and locatable pages no longer supported

Valid from Pega Version 8.1

@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.

Relevant records management shows more information

Valid from Pega Version 8.1

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.

Role-based workspaces improve productivity

Valid from Pega Version 8.1

You can now use workspaces to access role-based tools and features. By focusing on the tasks that align with your expertise, you can develop and manage your application more quickly.

For more information about the different types of workspaces, see Workspaces.

Feature management added to App Studio

Valid from Pega Version 8.1

You can now create and manage features in App Studio. Because this functionality is no longer restricted to Dev Studio, you can encourage all team members to adopt feature-driven development, which improves the traceability from your requirements to their respective implementations.

For more information, see Feature-driven development.

Application overview added to App Studio

Valid from Pega Version 8.1

High-level information about an application, such as the available channel interfaces, case types, and data types, is now available in App Studio. By monitoring your project from a holistic point of view, you can make informed decisions about how and where you want to allocate your development resources.


For more information, see Application overview.
 

Translation support added to application guides

Valid from Pega Version 8.1

You can now localize the content in your application guides. By referencing paragraphs instead of rich text in your chapters and tasks, you can provide guidance to users in their native language.

For more information about application guides, see Creating a guide for end users.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us