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.

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

Core Engine

Valid from Pega Version 7.1.4

This release contains fixes related to clipboard and declarative features, including data pages and autopopulate.

 

  • A rule may be changed using Private Checkout, and then checked into a higher RuleSet Version for that RuleSet.
  • Agents may now use a 24-hour time period for scheduling, as well as a 12-hour time period (which required the selection of AM or PM).
  • Caching and performance have been enhanced.
  • Declare expressions will work with embedded page lists when creating forms.
  • Mandatory parameters on a data page can handle blank values.
  • Properties may be auto-populated using a reference property which is created with a Property-Ref method in an activity.
  • System will use "private edit" rules in developer's personal RuleSet when that rule overrides the "standard" rule available to all.
  • The Page-Remove method will now remove Data Pages at the Thread level and the Requestor Level.
  • When copying a page using the "Set" action on a data transform, the Declare Indexes defined on that data will be updated.
  • When creating a data page, the Reload Once per Interaction checkbox can be checked to set the refresh strategy. 

Decision Management

Valid from Pega Version 7.1.4

This release contains a number of fixes that improve the configuration and execution of Batch decisions – specifically, a number of usability improvements and addresses some issues when creating strategies on IE8.  

  • Batch Decision functionality has been enhanced in the NBAM environment.
  • In NBAM, users can run the strategy execution batch based on the Seed list class instead of the customer class. 
  • Interaction data will now work even if Action or Organization  dimensions do not have values set.
  • Running a strategy which includes a Data Import of a structured page reference will work in batch mode.
  • Security was enhanced on the VBD Planner.
  • The Access of Role to Object rules have been enhanced to allow users to create new Dimension Operator records.
  • The NBAM Segment On Canvas will now fetch the SegMap data, even when the generated extended segment class has not been added to the Pages and Classes of the strategy.  The SegMap property will (if it exists) be added to a list of properties to fetch, even if the strategy indicates that it is not used.
  • When a strategy is defined on a customer class, users may now specify the list of required properties to fetch for the input definition.
  • When creating a new strategy, there is now a section to add a Strategy Results class like Business Issue or Group.

Designer Studio

Valid from Pega Version 7.1.4

Many refinements to the Designer Studio were made around performance and user experience. Based on feedback, we have made a number of bug fixes and strategic improvements that improve the overall user experience.

  • The Developer Portal connects to the PDN's RSS feed without needing a DigiCert certificate for validation. The RSS feed is just headlines; to open and read any of the articles, users will still have to log into the PDN.
  • Expression Builder has been enhanced to work with IE8.
  • New applications built in Version 7.1 will automatically redirect users to the PRPC login page upon logout. A new template has been added, to allow developers to customize their applications to redirect users to a logout page, if they wish.
  • Performance improvements were made when saving and validating rules.
  • Performance of the Guardrails Dashboard has been improved.
  • The display of circumstanced rules in Application Explorer has been enhanced.

New options to manage proposition validity

Valid from Pega Version 7.2.1

Manage your decisioning strategy more effectively with proposition validity settings. You can now set your propositions as always active, inactive, or active only within a defined time period. Setting a validity period for your propositions helps you to plan your strategy and automatically activate or deactivate propositions in the future.

For more information, see Proposition validity.

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.

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