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.

Existing collections are deprecated

Valid from Pega Version 7.1.7

The original implementation of the Collection form is deprecated. Legacy instances in your application remain functional; however, any new instance you create uses the redesigned Collection form. Use the Decision category in the Records Explorer to view all collections available to you.

For guidance on upgrade limitations, see the Deprecated Collection form.

Messages are rule resolved by class

Valid from Pega Version 7.1.7

As part of the Message form redesign, a class key part was introduced. While this key part is automatically handled as part of an upgrade or migration, it does change the available options you see in message SmartPrompts and how Rule-Message instances are rule resolved.

See Upgrade considerations for existing messages for more information.

Changes to archive.info in Pega 7.1.7

Valid from Pega Version 7.1.7

In Pega 7.1.7, the contents of the archive.info file have changed.

  • In versions Pega 7.1.6 and earlier, the archive.info file displays the build number of the Pega installation.
  • As of Pega 7.1.7, the build number no longer appears in the archive.info file.

In Pega 7.1.7, the archive.info file only displays a status message indicating whether or not the system is running, and the build number no longer appears. Instead, if the system is operational, the message “status=Running” displays in the archive.info file.

If there are any automated tests, scripts, or applications that rely on the archive.info file displaying the build number, those may fail and produce an error. It is recommended that any automation that relies on the build number displaying in the archive.info file be changed to look for the “status=Running” message.

End of support for form-based rule forms in Pega 7.1.9

Valid from Pega Version 7.1.9

Rule forms that are configured to render as forms are no longer supported in Designer Studio or end-user applications. Form-based configurations are found on custom rule types that were created in earlier versions of Pega 7 and are characterized by pop-up windows that are rendered externally from Designer Studio.

Reconfigure Pega 7 applications that use such rule forms by using standard harnesses and sections.

  1. Open the class form.
  2. Click the Advanced tab.
  3. Select Harness from the Rule formmenu.
  4. Create a new harness and new sections that implement the logic of the custom rule, using standard user interface layouts and controls.

Migrating custom rule forms to harnesses and sections offers the following benefits:

  • User interfaces become HTML5 WC3 compatible and responsive to different screen sizes.
  • User interfaces become cross-browser compatible, rendered consistently in Google Chrome, Mozilla Firefox, Apple Safari, and recent versions of Microsoft Internet Explorer.
  • Rendering performance on modern browsers is dramatically improved.
  • User interface pop-up behavior is eliminated; all windows are rendered inside Designer Studio and end-user applications.

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.

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

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