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

Unicode-enabled database for international language support

Valid from Pega Version 7.2.1

The Pega 7 Platform database has been enhanced to natively support Unicode multibyte character set encoding when using Postgres on Pega Cloud. This enhancement allows you to store data in languages such as Japanese, Chinese, and Korean.

Change the type of an existing field

Valid from Pega Version 7.2.1

You can now change the type of an existing field on the Data model tab of a case type or data type, resulting in a more efficient development process at design time. If there are any validation issues when changing a type, an error message is displayed, and the type cannot be modified by using this method.

For more information, see:

Open authoring for rule forms has been removed

Valid from Pega Version 7.2.1

Open authoring for rule forms has been removed. You can now edit decision tables and map values by using the application and supported browser of your choice; Microsoft ActiveX controls are no longer required. In addition, support for external XML, HTML, and Java IDE editors has been removed.

Pega Express application views simplify portal creation

Valid from Pega Version 7.2.1

Pega Express application views offer a simple, intuitive authoring experience for portals. Application view templates support responsive application development and offer mobile-specific templates. You can create portals by selecting from a predefined set of application view templates.

For more information, see Application views.

Rule form search

Valid from Pega Version 7.2.1

You can now search for content within some rule forms by clicking Search rule on the Actions menu. The search results and the tabs of the rule form that contain the search results are highlighted.

For example, you can find the properties that are used in a when condition inside an activity without navigating to each tab, when condition, transition, and method in the activity.

Delegate service-level agreements

Valid from Pega Version 7.2.1

You can now delegate service-level agreements (SLAs) to your business line by clicking Actions > Delegate. You can also delegate circumstanced versions of SLAs.

For more information about delegations, see Delegating a rule or data 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