Published Release Notes

Stage-related audit notes

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

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.

Quickly add an attachment step to your processes

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:

Add search fields to forms

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:

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

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

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.

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.

Using parameters to direct flow

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.

A single starting flow creates all ad hoc cases

An operator can uniformly create ad hoc cases in the My Cases area on the Case Manager portal, on user forms, and in Pega Pulse by way of the standard starting flow pySimpleCaseWorkFlow. Operators can define the routing of the case and an overall SLA when creating the case.

The default action created by the ad hoc flow contains a dashboard that also enables operators to quickly define tasks and add attachments.

Previously, the standard flows pyManualTaskStandardAssignment and pyManualTaskStandardApproval were employed. These are deprecated, but are still supported in existing configurations.

Convert cases to case types using the Configure for Reuse feature

An operator can use the Configure for Reuse feature available on the ad hoc dashboard and on the ad hoc user forms to convert an ad hoc case into a case type that can be reused throughout the organization.

An operator must belong to an access group references the standard pyPega-ProcessEngine:CaseDesigner role, which contains the privilege pyCaseInstitutionalize.

Calculate value mode "When invoked procedurally"

The calculate value mode named "When invoked procedurally" is available in Declare Expressions.

Expressions of this mode cannot be chained into or out of, and are triggered only when directly invoked by a collection rule (Rule-Declare-Collection).