Published Release Notes

More visibility of your production level

You can now see the production level of your environment in a new gadget that is available in all Pega Platform™ workspaces. To ensure that you immediately recognize your current environment, you can give it a unique name that is displayed when you click the gadget. In addition to specifying your production level and environment name on the System form in Dev Studio, you can now specify those values on the System & nodes page in Admin Studio.

For more information on Admin Studio, see Modifying your environment name and production level.

For more information on Dev Studio, see Specifying the production level.

Reuse when conditions when designing cases in App Studio

Reuse existing conditions to save time when you design a case in App Studio. Now you can use an existing when condition when you create a condition for a stage in your workflow. You can also define custom when conditions and save them for future use.

For more information, see Defining conditions with a condition builder.

Create multistep forms for stages

In Case Designer, you can now create multistep forms for a stage. Create several focused and concise screens to capture the information from users instead of using a single long screen. For example, you can ask users for their personal details in one screen, and then ask them to describe their medical condition in a separate screen. When you create a multistep form, choose a template to determine how the users navigate between screens.

For more information, see Adding a multistep form to a stage (for Dev Studio), Adding a multistep form to a stage (for App Studio).

Additional case settings in App Studio

You can now make it easier to distinguish your case type from other case types by customizing its icon and selecting a unique case ID prefix in the General case settings.

You can also access Locking and Notifications case settings in App Studio without switching to Dev Studio.

For more information, see:

• Changing the case ID format
• Changing the case icon
• Managing concurrent access to a case
• Enabling case notifications

Configure search for duplicate cases in the step property panel

You can now configure the search for duplicate cases in the step property panel. Save time by specifying search criteria that effectively identify potential duplicate cases.

At run time, make sure that each case represents a unique request by deciding whether to close the case as a duplicate, based on the criteria by which the system marked the case as a potential duplicate, for example, a matching email address.

For more information, see:

• For Dev Studio: Finding duplicate cases
• For App Studio: Finding duplicate cases

Visualize tasks more clearly with the task board view

In spaces and other contexts, you can now monitor and track the resolution of cases by using the task board view. This view groups tasks into columns by status to provide a visual overview for all members of a space. By default, the task board view is enabled in spaces, but you can enable it in any context to meet your needs.

For more information, see Monitoring and tracking cases (for App Studio) or Monitoring and tracking cases (for Dev Studio).

Rule revalidation after updating properties without restarting nodes

When you update certain property attributes, such as a property's maximum length, rule types that reference the property might not reflect the change. You do not always have to restart nodes to revalidate the referencing rules when they cannot be resaved, for example, when they are in a locked ruleset. For Pega Platform™ 8.1 and later, for non-stream rules, such as activities, data transforms, and so on, use the reassemble API in Admin Studio or truncate the assembled classes table.

For stream rules, such as sections, harnesses, paragraphs, and so on, reassemble the rules and restart the nodes. For more information, see More about properties.

For previous versions of Pega Platform, use the System Management Application (SMA) to revalidate stream and non-stream rules.

Make important content visible by promoting spaces

Now you can make highly relevant content more visible and more easily accessible with promoted spaces. Highlight promoted spaces on a separate tab in spaces to ensure that the most relevant content is quickly available and clearly organized. Promoted spaces are available for every user; however, only users with Super Admin privileges can promote a space.

For more information, see Granting Super Admin privileges.

Changes in JSON results when checking the health of your system

Beginning with Pega Platform™ 8.2, the JSON results that are returned when you ping a Pega Platform instance have changed. JSON results now include node type and health information, including test name, status, state, and node ID. The following samples show JSON results from versions before 8.2 and as of 8.2.

JSON results for pre-Pega Platform 8.2:

{ "duration":"3954.448601", "count":"0" }

JSON results for Pega Platform 8.2 and later:

{"node_type":["WebUser"],"health":[{"last_reported_time":"2019-02-14T16:10:49.589Z","test_name":"Sample-Stream-Check","status":"success"}],"state":"healthy","node_id":"10.10.10_samplenode"}.

Support for advanced validation of embedded and referenced data

To help you define validation conditions for a broader range of use case scenarios, Pega Platform™ now supports stage entry validation for embedded fields in the form of a validation matrix. You can now define validation conditions for both field groups and field group lists, and easily navigate between them. You can also select any fields and when conditions while building a condition for both field-level and stage-level validation.

For more information, see Validating field values for stage entry.