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.

Post files and links with pxPostMessage API

Valid from Pega Version 7.1.4

The pxPostMessageAPI now supports text messages, file attachments, and hyperlinks. You can programmatically update Pulse streams using this API from activities or SLA rules.

Create, Save As, and Specialization forms

Valid from Pega Version 7.1.4

The familiar “New” and “Save As” forms have been streamlined to make record creation faster and more intuitive. You can easily target a specific layer in your application stack, interactively define the record’s configuration and select only those circumstance definitions that make sense for your use case.

While the underlying behavior for creating a record is not new for this release, the redesigned UI of these forms and new defaulting strategy for fields is worth noting:

PRPC_7_1_4_Release_Notes-1.jpg

To launch these forms, use one of the new options found in the action area of the form header:

PRPC_7_1_4_Release_Notes-2.jpg

Note that not all record types support the ability to specialize by circumstance.

For more guidance on how to use the Create, Save As and Specialization forms, please refer to: Intuitive record creation and specialization

Quickly create ad-hoc cases

Valid from Pega Version 7.1.4

The My Cases work area on the Case Manager portal introduces a Quick Create feature that lets users create cases and assign tasks that are not included in the processing of business cases (instances of case types defined in the Cases Explorer).  For example, a manager can create a case and a task to set up a phone conference with her staff, or a reminder to enroll in an online seminar. Users can also set up a series of tasks to represent all they work they need to do to accomplish a specific goal.

Redirect users to logout screen

Valid from Pega Version 7.1.4

New applications built in Version 7.1 will automatically redirect users to the PRPC login page upon logout.

 

A new template, Web-Session-Return-Template, has been added, to allow developers to customize their applications to redirect users to a logout page, if they wish.  This template can be copied to a ruleset visible to unauthenticated requestors (via node configuration) and used to override Web-Session-Return.

Pinned classes in Application Explorer

Valid from Pega Version 7.1.6

The Application Explorer now includes a Pinned Classes section. This feature allows you to interact with a customized list of classes without having to explicitly switch context in the explorer.

Ability to deprecate a rule

Valid from Pega Version 7.1.6

You can deprecate any Rule- instance to indicate that it is no longer supported.

Users are warned when they open or reference a deprecated rule instance.

Ability to deprecate a class

Valid from Pega Version 7.1.6

You can deprecate any Rule- class to block users from creating new rule instances.

Users are warned when they open the class rule form or any instance of the class.

Only classes that do not belong to a class group can be deprecated.

Designer Studio responds to deprecated rules

Valid from Pega Version 7.1.6

Deprecated classes and rule instances in Pega- rulesets are excluded from:

  • Search results
  • Application Explorer results
  • Lists launched from the Records Explorer
  • +Create menus

These restrictions do not apply to classes and rule instances deprecated in your application rulesets.

Retired Six R's

Valid from Pega Version 7.1.6

The Designer Studio > Application > Inventory > Six R's landing page has been retired.

Integration landing page updates

Valid from Pega Version 7.1.6

The following features and wizards now launch as landing pages in the Designer Studio:

Designer StudioIntegration > Tools > Wizard cleanup

Designer StudioIntegration > Email > Email Accounts

Designer StudioIntegration > Email > Email Listeners

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