Published Release Notes

Caching of common rules in offline mobile apps

To help start offline-enabled mobile apps more quickly from the time when the server was started, you can now cache common Pega 7 Platform rules, including node scope data pages. Optionally, you can also either cache all node scope data pages, with the exception of the selected ones, or cache only the node scope data pages that are explicitly specified. You set up the offline caching options for your custom mobile app in the Advanced tab of the Access Group rule form.

For more information, see the Offline Configuration section in Access Group form - Completing the Advanced tab.

Deploy in secured mode

Deploying the Pega 7 Platform in secured mode helps prevent unauthorized access to your system. By default, the Pega 7 Platform deploys in secured mode. For more information, see the Deployment Guide for your environment.

Create case and Wait smart shapes available in Case Designer

Two smart shapes have been added in Case Designer. Use the Create case smart shape in a case step to create another case, a child case, or multiple child cases. Use the Wait smart shape to pause the process of a case under specified conditions.

For more information, see Adding a preconfigured step to a process.

Use standard Developer portal

Customized versions of the Developer portal rely on legacy components and are not supported.

To avoid backwards compatibility issues, update your access group to point to the standard Developer portal prior to upgrade.

Run advanced agents on only one node in a cluster

You can now configure an advanced agent to run on only one node in a cluster at a specified time. In addition, you can specify the time interval within which an advanced agent runs on only one node in the cluster, which avoids having two advanced agents starting to run on the same node at the same time.

For more information, see Improved control for running advanced agents and Agents rules – Completing the Schedule tab.

New PegaRULES:PegaAPISysAdmin​ role

The role PegaRULES:PegaAPISysAdmin​ has been added to the Pega 7 Platform. This required role gives system administrators access to the Pega API REST User Services and is not required for other services.

For more information, see Securing the Pega API.

Create case and Wait smart shapes are available for stage steps

You can design case types more efficiently by using smart shapes, which are steps with preconfigured functionality. Use the Create case step to create a case from an existing case type, or to create a new case type, and transfer information from the original case to the new one. Use the Wait step to pause case processing until another case reaches a specified status.

For more information, see Adding a preconfigured step to a process.

New interaction history attribute

Pega^® Platform 7.4 introduces the pySubjectType attribute that is used in interaction history aggregations. This attribute is populated for interaction history records that were created in release 7.4. For records that originated in earlier releases, the attribute must be set in the following scenarios:

• Single-level decisioning frameworks that use interaction history.
• Multi-level decisioning frameworks where interaction history is used by two or more levels of strategies that are defined on different classes.

For the single-level scenario, configure the Dynamic System Setting that sets the pySubjectType attribute when your framework reads interaction history records. The value of this Dynamic System Setting becomes the name of the customer class.

For the multi-level scenario, update the database table for all strategy levels manually. For each level, make sure that the value in the Subject Type column is set to the name of the class for the corresponding strategy. For example, the value for the top level strategy should be set to the name of the class of that strategy.

For more information about interaction history aggregations, see Data Sources landing page

For more information about multi-line strategies and contexts, see Strategy components - Embedded strategy

Upgrade changes system name

As of Pega 7.1.7, the following renaming behavior no longer occurs.

The upgrade process renames your system to “PRPC” and modifies any custom requestor rules in your application to use this name. After the upgrade completes, you must apply these changes to revert your system:

1. Identify all custom requestor rules (browser, batch, app, portal) with access groups that point to prior versions of PRPC.
2. Open the relevant access groups (for example, PRPC:Unauthenticated and PRPC:Agents) and update the name and version fields to point to the current PegaRULES application.
3. Reset your system name to its original value. You can set the Dynamic System Setting prconfig/identification/systemName/default or use the Designer Studio > System > Settings > System Name landing page.
4. Restart the system.

Limited action set for mobile-optimized grid layouts

The grid layout supports a limited action set when you select the Optimize for mobile mode. Actions allow you to determine the behavior of the grid. When Optimize for mobile is selected on the General tab of the grid layout properties, the following actions are available on the Actions tab:

• Set focus
• Open work by handle
• Open assignment
• Edit item

For more information, see Optimize repeating grid layouts for mobile.