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. 

DCO

Valid from Pega Version 7.1.4

This release focused on improving the user experience of creating new rules and tightening up the use of specifications in the Case Designer.  The layout of the New and Save As forms were made more intuitive and intelligent.  Specification actions were made to be more consistent across various aspects of the Case Designer.

  • After removing specification references, users can create and save a new specification.
  • Developers may now choose either an existing specification or create a new one for subflows and Split-For-Each shapes.
  • If a specification is not associated with flow shapes such as sub flows, Utilities, or Split-For-Each, it is possible to import speciications with the same names, and the flow shapes will default to using those imported specs.
  • In the outline view, specification changes will be preserved when switching from tab to tab.
  • The View Full Details functionality from either Configure Step or the Outline View will display all details, including the specification requirement links.

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.

Reporting & Data

Valid from Pega Version 7.1.4

This release fixed many existing unlocalizable elements in 7.1 reporting interfaces (The Report Viewer, Report Editor, Chart Editor, and the Report Browser) and now they are fully localizable. Changes were made to make Listview, summaryview,  and report viewer display possible WCAG 2.0 level A and AA support.

  • Parameters may now be used in a sub-report join condition.
  • Report Definition localization has been enhanced.
  • Standalone ListViews with embedded SmartInfo have been improved to resize appropriately when the SmartInfo section is expanded.
  • The data section of a report will now display in all of the available space when a fixed header option is selected.
  • When localizing a listview with filters, tool tips are translated.

BIX performance improvements for CSV output in the Pega Cloud

Valid from Pega Version 7.2.1

BIX performance has been enhanced to download up to 25 GB of data per hour for extracts from a BLOB-less class table for CSV output. This high-throughput option is available only for Pega Cloud instances that use a Postgres database. This option is used automatically for these types of extracts.

When this option is used, the –x and –c command-line options for BIX are not supported, and the checkSum field in the manifest summary is not populated. If you need these options, you can revert to the previous implementation by using a setting in the prconfig.xml file.

For more information, see BIX high-throughput data downloads in the Pega Cloud.

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.

Improvements to the Document Application tool

Valid from Pega Version 7.2.1

Application profile documents and application documents generated by the Document Application tool have been improved to present information in a more logical order based on how the application was built (for example, by case life-cycle management). Also, these types of documents now include all specifications linked with an implementation rule, presented in logical order under the implementation rule.

In addition, to help you more efficiently drive decisions by stakeholders, you can specify whether to include related built-on application layer assets in application profile documents and application documents. For specification documents, you can specify whether to include specifications from the built-on application layer.

For more information, see Document Application tool.

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