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.

Tracked changes persist between client sessions

Valid from Pega Version 7.1.7

The Microsoft Word native change tracking feature persists between client sessions for specifications. Enable this feature to facilitate collaborative reviews of your specifications with project stakeholders.

Inserting your specification updates as tracked changes allows you to:

  • Provide visible markup to the next reviewer.
  • Correlate edits to a specific user and time.
  • Generate documents that include markup and comments.

Local settings, such as the colors you specify for markup, do not persist between clients.

For instructions on how to prevent markup and comments from appearing in generated documents, see Advanced options for editing specifications.

Add multiple attachments at once

Valid from Pega Version 7.1.7

You can now add more than one attachment to a requirement or specification at a time, without closing the Add/Edit Attachment modal dialog box. Use the traditional browse method to upload an attachment or drag and drop a local file, based on your needs. View and access your attachments from the Application Profile landing page, Requirement form, or Specification form.

Plan projects using release data

Valid from Pega Version 7.1.7

Requirements and specifications can now be mapped to a target release and iteration within a specific release. Populating these fields allows you to set and publish a release schedule through worksheets generated by the Sizing wizard. Access these fields from the Application Profile landing page or by opening any requirement or specification.

The Release and Iteration fields as they appear in a specification and a corresponding worksheet

The Sizing wizard incorporates values from the Release and Iteration fields for specifications only.

Specification type extended for decisioning users

Valid from Pega Version 7.1.7

Specifications now support a Decision Strategy Manager (DSM) type. This allows you to map your specifications to a decisioning component, such as a strategy or model. After you select an appropriate subtype and provide relevant metadata, you can run the Sizing wizard to incorporate these details into project sizing worksheets.

DSM specification details as they appear in the Specification form and Sizing wizard output

You must have access to Decision Management rulesets to create DSM specifications. For more information on specification types, refer to the Details tab of the Specification form. To view all specifications in your application, filtered by type, refer to the Application Profile landing page.

Add collections as linked implementations

Valid from Pega Version 7.1.7

You can now identify a collection or individual steps within a collection as an implementation of a specification. Linking specifications to rules allows you to more accurately convey your application design to project stakeholders. Use the Specifications tab on the Collection form to create these links.

To see all implementations for a given specification, refer to the Application Profile landing page or the Implementations tab of the Specification form.

Add project branding to generated documents

Valid from Pega Version 7.1.7

The standard Word Template for specification descriptions is now extensible. Using a customized template allows you to brand your generated documents with project-specific elements.

Specialize the Rule-Application-UseCase.pySpecificationDescription rule to:

Generated document with custom company logo

Refer to Advanced options for editing specifications for instructions on how to override this template.

Offline mobile apps require Dynamic Container to use frameless Single Document mode

Valid from Pega Version 7.1.7

You can add a Dynamic Container (DC) directly into a Dynamic Layout cell. When creating a custom mobile app with offline capability, you must use the frameless Single Document mode of DC.

Note that mobile offline capability does not support using a framed Single Document mode.

Push notification delivery to multiple devices

Valid from Pega Version 7.2.1

Push notifications sent from the Pega 7 Platform are now delivered to all devices on which a user is logged in to your custom mobile app, regardless of the device platform. You can either send push notifications from the Push Console to all users who have your application installed on their devices, or configure your application to send push notifications to indicate that an action might be required, a status update is available, or a case was approved.

Support for subflows and decision flow results in offline mobile apps

Valid from Pega Version 7.2.1

Subflows in offline-enabled mobile apps are now supported to perform additional tasks outside of the main flow. The subflow can run only on the current work item, with the subflow displaying in the main flow, in a nested subflow, or located next to an assignment. No likelihood routing is supported for subflows. It is also possible to set a flow result by using the pega.process.flow.setFlowEndStatus() JavaScript method to override the status set by a property in the subflow's end shape. The process engine also takes into account the likelihood setting if the flow result is conflicting or absent, provided the flow result is not in a subflow.

For more information, see Flow processing in offline mode.

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