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.

Use "alternate database" as report source

Valid from Pega Version 7.1.6

You can opt to use the the "alternate database" identified in the Reports Database field of the Data-Admin-DB-Table instance that supports the Applies To class of a report as the source for the report. This reduces the load on the database that serves your application when you run the report.

Attachment support for requirements

Valid from Pega Version 7.1.6

Requirements now support attachments. You can add attachments from the Designer Studio > Application > Profile > Requirements landing page, the Add/Edit Requirement modal, or the requirement rule form.

Enhanced document generation

Valid from Pega Version 7.1.6

The following usability improvements have been made to documents generated by the Application Document Wizard:

  • Stages and Processes now appear for case types that use Case Lifecycle Management. This diagram includes hyperlinks to corresponding sections in the document and is scoped to top-level processes only.
  • All flows (excluding pyStartCase) referenced by a case type now appear in documents. This removes previous constraints on non-starting, draft, and checked out flows.
  • Entity Relationship Diagrams (ERDs) are now embedded in documents as Visio objects.
  • Sections without content are omitted from the generated document.
  • Screenshots are labeled.
  • Requirement text (Long Description) is included in the Requirements Matrix section.
  • Linked requirements appear in context beneath their associated specification.
  • Acceptance Criteria appears in context beneath the associated specification, report, or correspondence item.

Stage-related audit notes

Valid from Pega Version 7.1.6

History notes for the following stage-related process steps appear on the user form's Audit tab:

  • Automatic Stage Transition
  • Manual Stage Transition
  • Process Stage Transition
  • Stage Skipped
  • Stage Started

You can select the ones you want to turn off for a given case type by copying the standard decision tree Work-.FilterHistory to your application ruleset and updating the above parameter entries.

Redesigned Process Modeler property panels

Valid from Pega Version 7.1.6

Process Modeler property panels have been reorganized so that it's easier to find the properties and fields you're likely to want, and quickly create the configuration you need. To enhance ease of use:

  • Tabs were eliminated.
  • All fields are located on a single panel and are grouped by their function.
  • The most commonly used fields appear at the top of the panel and are clearly visible.
  • Field and functionality of interest to advanced users are organized into an expandable Advanced section positioned at the bottom of the panel.
  • Business-friendly labels and headings, and instructional text make it easier for non-technical users to quickly understand the meaning and purpose of each field.

113786_assignmentpanel.png

Quickly add an attachment step to your processes

Valid from Pega Version 7.1.6

The Attachment step allows you to quickly add an Attach Content subprocess to your flow. Once added, choose the attachment type and instructions to present to users:

113931_attachment.png

Add search fields to forms

Valid from Pega Version 7.1.6

A Search field type is available in the Form Configuration dialog. This field enables users to search for and select a specific record from a list-type data page. Configuration is straightforward, as shown below:

113936_SearchField.png

At runtime, users search on the key field and any additional specified search fields. The user interface automatically refreshes, enabling dynamic results when selecting a search field.

Service level available for flows

Valid from Pega Version 7.1.6

Service level agreements can now be associated with individual flows. This feature is especially useful for establishing goals and deadlines for flows within a stage-based process. The setting is located on the flow record Process tab.

Track the geolocation of audit trail actions

Valid from Pega Version 7.1.6

The geolocation tracking feature allows you to capture latitude and longitude information each time a requestor entry is recorded in the audit trail. A Map it link appears in the Location column on the Audit tab's History tab. Clicking the link renders a Google Map that displays the location based on the coordinates.

To enable this feature, copy the standard when rule pyGeolocationTrackingIsEnabled to your application. You can customize the "default always true" condition to suit your requirements. For example, you can set up a privilege or role that tracks only mobile users rather than all users.

113946_geolocator.png

When you use Application Express to create a new application built on a standard Pega application (such as PegaRULES or PegaDM), the system enables geolocation tracking for all case types. You can disable or enable tracking at the case type level using the Geolocation tracking setting on the Case Designer Details tab.

To enable "Map it" functionality, create a dynamic system setting that contains your Google Map API license key.

Using parameters to direct flow

Valid from Pega Version 7.1.6

You can use a parameter rather than a stage name to direct the flow in the Change Stage Smart Shape. Select the Other option in the Select a stage field to specify the parameter.

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