Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

Case Manager option for searching only attachments

Valid from Pega Version 7.2

Case Manager search now has an option to search only case attachments. When you search attachments, a new column in the search results displays a paperclip icon with the number of attachments that match the search string. You can click the number to display a list of matching attachments for the selected case.

The Declarative Network display is now cross-browser compatible

Valid from Pega Version 7.2

The Declarative Network display can now be displayed on all browsers.

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.

Use multiple built-on applications to enhance ruleset reuse

Valid from Pega Version 7.2

Applications can now have multiple built-on applications, allowing rules to be reused as a part of a built-on application at run time while being developed independently at design time.

Previously, applications built in Pega 7.1 and earlier versions were assembled in a single linear application stack--one application built on top of another application, and so on. Attempting to reuse rulesets and frameworks across applications resulted in having to splice applications together, creating challenges when attempting to support the use of these custom created applications. Starting in Pega 7.2, applications are built on to other applications by using a hierarchical tree structure, and the Pega 7 Platform automatically converts this tree into a linear application stack.

For more information, see Using multiple built-on applications and the Ruleset behavior at design time section in Application stack hierarchy for multiple built-on applications.

New Pulse gadgets for developers

Valid from Pega Version 7.2

Pulse for the Pega 7 Platform provides two new gadgets: pxContextFeed and pxActivityFeed.

The pxContextFeed gadget is a section that you can integrate with your application. Users can use this gadget to communicate with other users by creating and sharing posts within a given context. You can also customize the gadget or build your own Pulse interface by using a number of APIs.

The pxActivityFeed gadget aggregates all the activity feeds for the cases that a user follows without requiring that individual cases for posts be viewed.

For more information, see the help topic Pulse gadgets and custom APIs.

Support for delegating map values, correspondence rules, and circumstances

Valid from Pega Version 7.2

You can now delegate map values and correspondence rules from the Actions > Delegate menu. In addition, you can delegate circumstanced types of the following supported rules and data types:

  • Map values
  • Correspondence rules
  • Paragraphs
  • Decision tables
  • Data types

New Pulse gadget for users

Valid from Pega Version 7.2

You can use Pulse to communicate and collaborate with other users. For example, in Pulse you can post messages, share files, select cases for which you want to receive emails, search for content, and view an activity feed in your dashboard that aggregates your Pulse posts.

For more information, see Pulse for social collaboration.

New types of steps in a process

Valid from Pega Version 7.2

You can add assignments, subprocesses, and preconfigured steps to a process in Case Designer. By using these new step types, you can quickly enhance your case life cycle and identify opportunities for reuse. This change also delivers a more consistent experience to users who are working in Case Designer and Process Modeler.

For more information, see Steps in the life cycle of a case.

Reusable components in a case life cycle

Valid from Pega Version 7.2

You can easily add an existing process or user action to the life cycle of a case type. By reusing functionality in your application, you can reduce the time that it takes to configure a case type.

For more information, see Steps in the life cycle of a case.

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.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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