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.

Business logic-based routing cards enhancements

Valid from Pega Version 8.5

To ensure that the sequence of business logic-based routing cards conforms to your business requirements, you now have the option to change the order of the cards. For easier navigation across multiple routing cards, the system automatically collapses the cards for you, and you can then easily expand the cards that you need to display.

For more information, see Navigate easier across business logic-based routing cards (8.5), Assigning users automatically at run time.

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

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.

Source field not displaying in data transform

Valid from Pega Version 7.1.4

On the Data Transform rule form when using the Update Page action, if the Relation value is updated to “with values from”, the Source field will not be displayed.

(Note that for existing data transforms where the Source field has already been completed, this situation should not occur.)

Workaround

  1. Below is a data transform that has been configured to use Update Page.
    DataTransform1.jpg
  2. If a user were to choose an alternate source by updating the ‘with values from’ Relation value, they would not be prompted to provide a page name in the Source field.
    DataTransform2.jpg
  3. At this point, to be able to enter the Source page value, the user has to save the rule, which results in an error because the source page value is blank. This causes the field to appear.
    DataTransform3.jpg
  4. Once the field has appeared, the Source page value can be provided, and the form can be saved successfully.
    DataTransform4.jpg

Add subspaces within spaces

Valid from Pega Version 8.2

You can now create subspaces within spaces. By adding a subspace, you can collaborate on a subtopic that is related to the topic of the parent space. For example, you can create an Annual Day subspace within the Events space.

For more information, see Creating a subspace.

Improve clipboard performance for Service REST

Valid from Pega Version 8.2

Improve clipboard performance in Service REST processing by using the new Lightweight clipboard mode option. This mode does not support all clipboard features.

For a list of supported and unsupported features, see Service REST form - Completing the Service tab.

Support for large binary data item storage in Pega Client for Windows

Valid from Pega Version 8.2

Pega Client for Windows can now store and synchronize large binary data items and their corresponding actions from the action queue. As a result, offline-enabled application users can view, attach, and delete data files from within a case view, whether the Windows-based device is online or offline. To use this feature, enable offline case attachment support, which allows offline-enabled applications to synchronize case attachments between Pega Platform™ and the device.

For more information, see Attach content support in offline mode and Enabling offline case attachments support.

Visualize application layers for case processes and sections

Valid from Pega Version 8.2

In App Studio, you can now easily visualize the application layers for case processes and sections, including work areas and views. When you click the Discover gadget for a case process or section, you are shown a visual representation of the application layers. You can open a layer in Dev Studio to see the rulesets and other attributes of an application.

For more information, see Discover gadget.

Date range configuration added to DateTime control

Valid from Pega Version 8.2

The DateTime (calendar) control now includes an option to specify a custom date range. The users will be able to quickly select valid start and end days of a period by choosing dates in an interactive calendar in an overlay.

For more information, see Configuring the basic settings for a DateTime control - date range

Enhanced SLA settings in App Studio

Valid from Pega Version 8.2

You can now reuse existing service-level agreements for assignments and approvals in App Studio without switching to Dev Studio. For example, you can select an action that the system performs when a task goal or deadline is past due, such as reassigning the task to a different user.

For more information, see Setting goals and deadlines for task completion and Defining an escalation action for an incomplete task.

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