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.

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.

Device preview includes a configurable list of common mobile devices

Valid from Pega Version 7.2.1

Pega Express device preview displays your application in a simulated mobile device. By previewing your application, you can view the user experience on a desktop, tablet, or phone. You can select from a list of common devices or add devices to the list by editing Pega-DevicePreview-Device.

For more information, see Previewing an application on a mobile device.

Associate specifications on implementation rule forms

Valid from Pega Version 7.2.1

You can now view, add, and delete the specifications that are associated with a rule on the new Specifications tab of most rule forms. The Specifications tab is available for almost all implementation rules, except for administrative and deprecated rule types. By associating specifications with the rules that implement them, you improve the end-to-end traceability of your specifications.

For more information, see Associating specifications on implementation rule forms.

Ignore browser and operator locale to display Designer Studio in English

Valid from Pega Version 7.2.1

The operator preferences configuration includes the option to ignore the browser and operator locale. Some rulesets are shared between Designer Studio and end-user portals. Translated words might occasionally display in Designer Studio. Selecting the Ignore locale check box ignores the locale of the operator and browser to display Designer Studio portals in U.S. English only.

For more information, see Updating Designer Studio preferences.

Flexbox layout mode for dynamic layouts

Valid from Pega Version 7.2.1

The flexbox layout mode is available for dynamic layouts and is now the default layout mode for newly created dynamic layouts. In a flexbox layout, sections contained within the layout can grow or shrink to fit the available space, providing a more efficient way to distribute space between items in a container. Existing dynamic layouts can be converted to the flexbox layout mode. You can configure the layout mode on the Presentation tab of the Dynamic Layout property panel.

For more information, see Dynamic Layout Properties — Presentation tab.

Harness settings container format includes option for no markup

Valid from Pega Version 7.2.1

The harness container format includes a No markup option. This option removes the non-semantic table tags from the container header, making it more consistent with current UX best practices. The No markup option is required for the new flexbox-based dynamic layouts to work correctly in Internet Explorer 11.

For more information, see Harness form — Adding a container.

Field value inspector in Live UI

Valid from Pega Version 7.2.1

Easily identify and translate field values with the field value inspector. You can also use the field value inspector to validate translations and update missing or incorrect translations. The field value inspector is on the Localize tab of Live UI.

For more information, see Field Value Inspector.

Categorize repeating dynamic layouts

Valid from Pega Version 7.2.1

Rows of a repeating dynamic layout can be categorized by a property. Categorization is useful for creating date-based navigation or categorizing list items. You can also set the maximum height of a repeating dynamic layout in the Presentation tab of the repeating dynamic layout properties. You configure categorization on the Operations tab of the repeating dynamic layout.

For more information see Repeating dynamic layout - Operations tab.

Build consistent, high-quality sections with design templates

Valid from Pega Version 7.2.2

The Pega 7 Platform provides predefined design templates that you can apply to your sections. Templates eliminate the need to design or copy another layout each time you want to design a section. You also can create custom design templates that can be shared with other users. Custom templates can contain regions (dynamic layouts) that you can further customize for each section.

For more information, see Designing sections by using design templates.

Improved scrollable layouts in a new harness

Valid from Pega Version 7.2.2

By default, you can now create a new harness with a screen layout instead of as a container with a cell structure. This change ensures that you can create an application layout more efficiently; for example, you can specify a scroll area exactly the way you want in a desktop application or a mobile app. You can arrange the header, footer, and main area content at the new harness level by using sections. For example, you can specify headers and footers to be fixed or to scroll with the page. New layout options are configurable in the skin. Different layout selections are available when you use the harness as an app view, a main area, inner harness, or a page view.

For more information, see Configuring a screen layout.

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