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.

Flow rules not supported in IE8

Valid from Pega Version 7.1.1

In versions prior to 7.1.2, flow rules do not open in Internet Explorer 8 (IE8). Upgrade your system to the latest version of PRPC or access flows from another supported browser.

Discontinued support for list view and summary view rules

Valid from Pega Version 7.2

The list view rule and the summary view rule are deprecated, and support for these rules has been discontinued. Existing list view and summary view reports will continue to work on supported browsers. However, the last version of Internet Explorer that list view and summary view rules support is Internet Explorer 11.

You cannot create new list view or summary view reports. Instead, create list reports and summarized reports by using the report definition rule. To prevent display issues, re-create the custom list view and summary view reports that you need as report definition reports.

Label changes to field types in Case Designer

Valid from Pega Version 7.2

The following field types have been renamed in Case Designer to be consistent with Data Designer and other areas of the Pega 7 Platform.

Label in previous versionsLabel in Pega 7.2
TextText (single line)
Text (multiple lines)Text (paragraph)
Check boxBoolean
Date and timeDate & time
DateDate only
Drop downPicklist
Number (integer)Integer
Number (decimal)Decimal

Users who upgrade from versions prior to Pega 7.2 do not have to take any action because the label changes are cosmetic and do not affect the underlying controls or property types that support form building.

For more information about the field types that you can use when building a form, see Storage and display of single-value fields.

Process Outline view is unavailable

Valid from Pega Version 7.2

Process Outline view is no longer available as of this release. Use Case Designer instead to configure your processes. For advanced options, you can open the underlying flow for a process in Process Modeler.

For more information, see Designing a case type and Diagram tab on the Flow form.

New location for case-type settings

Valid from Pega Version 7.2

The configuration options for case-type settings have been moved from the property panel to the Settings tab in Case Designer. This change separates behavioral settings from life-cycle settings so that you can stay focused as you design your case types.

For more information, see Configuring case-type behavior.

No private posts in new Pulse gadget

Valid from Pega Version 7.2

The new Pulse gadget does not support private posts. When you upgrade to the new gadget, any private posts of the following types that you created by using the previous version of the gadget become public.

  • Operator posts
  • Case posts
  • Posts that used the generic pxPostMessage API with private posts enabled
  • Posts that used the Pulse smart shape in PRPC 6.3 or earlier with private posts enabled

For more information about the new Pulse gadgets for developers, Pulse gadgets and custom APIs.

For more information about the using the new Pulse gadget, see Communicating with Pulse.

Atom Server and SOAP Server rule forms are deprecated

Valid from Pega Version 7.2

The Atom Server and SOAP Server rule forms are deprecated. Use the Connect CMIS rule form instead.

Existing rules that were created with the deprecated forms still work, but you cannot create new ones.

Processes run by default when a stage is restarted

Valid from Pega Version 7.2

The Run on re-entry check box in Case Designer has been removed. As a result of this change, processes run by default each time that a stage is restarted. Users who previously had this check box cleared can use the Start when option in Case Designer instead to define the criteria for skipping a process.

For more information, see Adding a process to a stage.

Conversion of single-step assignments is no longer required

Valid from Pega Version 7.2

You no longer need to create a single-step assignment in a case type and then convert it to another supported step type. Instead, you can use the + Add step option in Case Designer to add any step type directly to a process in a stage. This change delivers a more consistent experience to users who are working in Case Designer and Process Modeler.

The following table lists the step labels in Case Designer that were updated to support this change.

Step label in previous versions

Step label in Pega 7.2

Single-step assignmentCollect information
ApprovalApprove/Reject
AttachmentAttach Content
CaseCreate Cases

For more information, see Adding a step to a process in a stage.

Customizations to the prlogging.xml file must be manually ported after upgrade

Valid from Pega Version 7.3

As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, the name of the logging configuration file has changed from prlogging.xml to prlog4j2.xml and the format of the file has changed considerably. If you customized your prlogging.xml file, port the customizations to the new prlog4j2.xml file. If you do not port the changes, the Pega® Platform uses the default prlog4j2.xml file and disregards your customized prlogging.xml file.

For more information about customizing your log files, see the Apache Log4j 2 documentation.

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