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.

DCO and PMF integration is unavailable

Valid from Pega Version 7.1.5

DCO and PMF integration functionality is not available in this release. Related project management controls have been removed from the following:

  • System Settings landing page (Designer Studio > System > Settings > Project Management)
  • Application Profile landing page (Designer Studio > Application > Profile > Specifications)
  • Add/Edit Specification dialog

Stages and Steps may not appear as expected

Valid from Pega Version 7.1.5

There are some unique configurations of the newly enhanced pxDisplayStages gadget that can lead to case type "Stages and Steps" appearing more than once or not at all.  In the event that your application experiences one of these scenarios, the recommended work around is to relocate the gadget:

  • Add pxDisplayStages to the pyCaseContainer section (or equivalent)
  • Remove pxDisplayStages from the pyCaseActionArea section (or equivalent).

Text Input control number type does not validate

Valid from Pega Version 7.1.5

When a Text Input control type is set to "Number" in the Presentation tab:

  • Validation does not trigger and the field is blanked out when a user submits the form.
  • If a value other than a number is entered, the browser sends an empty value, and the value is not validated.
  • In the Clipboard, the field value displays as empty.
  • If the field is required, the validation displays.

This issue occurs when using both the Chrome and Safari web browsers, and is a result of browser behavior for the HTML5 type=“number”. To fix this issue when using these browsers, do not use the "Number" type in Presentation tab of a Text Input control. Instead, the type should be set to "Text".

Unclear error message when saving shared class instance in tenant layer

Valid from Pega Version 7.1.5

If you attempt to save a shared class instance from the tenant layer, Pega 7 displays this message:

This record has x errors. Save Failed: There was a problem saving an instance of class: Error Code: <none> SQL State: <none> Message: <none>

You cannot save a shared instance from the tenant layer if that instance cannot be overridden.

Screenshot generation runs on local client

Valid from Pega Version 7.1.8

If you generate screenshots to include in your application document, this process still runs on your local client. Additionally, you are still required to use Internet Explorer to use this feature.

Warning message when opening server-generated documents

Valid from Pega Version 7.1.8

Depending on your system configuration, the following warning message might be displayed when you open a document that was generated on the server.

If you click No, certain content (for example, Table of Contents) is not populated in the document. Instead, click Yes and save the document.

Warning message dialog

The warning message that displays

Number and text input controls on Android devices may not display the correct keyboard

Valid from Pega Version 7.1.8

When running a Pega 7 application on a device using the Android operating system, pxNumber and pxTextInput controls may not display when using the desired on-screen keyboard. This happens when the number or text input type is set to number.

At design time, the input type is selected in the Editable Format section of the Presentation tab in the Cell Properties panel for a pxNumber or pxTextInput control. Due to a known limitation in some versions of the Android OS running on some devices, the keyboard displayed at run time may not support entry of decimal values when a Number type keyboard is specified.

To resolve this issue, use the Phone type when numbers with decimal values may be required. Using the Phone type displays a numerical phone keyboard. The Android phone keyboard includes both commas and periods so that decimals may be entered.

Cell Properties dialog

The Phone type selected in the Presentation tab of a Number control

Note that this issue only occurs on Android devices. It is recommended that applications for iOS continue to use type=“Number”.

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.

Deprecated rule types

Valid from Pega Version 7.1.8

The following rule types have been deprecated as of the Pega 7.1.8 release:

  • Form
  • Hierarchy
  • Service COM
  • Service BPEL
  • Connect BPEL
  • Parse Transform
  • Parse Transform Collection
  • Parse Infer

For more information, including suggested alternate rule types, see the help topic Deprecated features.

Search field type is deprecated

Valid from Pega Version 7.1.9

The search field type in Form Builder is deprecated. Use a data reference or user reference instead, both of which prompt users with an autocomplete field at run time.

For the full list of supported field types in Form Builder, see Supported display modes by field type.

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