Published Release Notes

Node classification replaces NodeID-based configuration

For simpler cluster administration and better application resiliency, Pega^® Platform is moving toward a node classification model. Although agents will continue to work by using NodeIDs for several upcoming releases, use node types instead of NodeID configuration for agents, listeners, and decisioning services for more efficient operations and upgrades.

For more information, see Node classification.

Aggregate data in interaction history summaries

You can now group, aggregate, and filter interaction history data in a single strategy component. By using interaction history summaries, you can create refined data sets that simplify strategy frameworks and accelerate decision-making. Aggregated data sets are easier to process, manage, and troubleshoot.

For more information, see Data Sources landing page

The worklist appears to be empty when you go back from an opened case in an offline-enabled mobile application

In a Pega^® Platform offline-enabled application, when you go back to the worklist from an opened case, the worklist appears to be empty even though it contains cases. This issue will be fixed in the next release of Pega Platform. Only portals that use the key principles and design of the pyCaseWorker portal are supported in offline-enabled applications.

For more information, see Offline mobility guidelines.

Preflight optimization extended to actions

The preflight optimization process now excludes JavaScript for actions that are not used in the application. To enable preflight optimization, click Designer Studio > User Interface > Application readiness > Preflight optimization.

For more information, see Optimizing application load time.

New shape on the strategy canvas

The Strategy rule has been enhanced with the Embedded strategy shape, which simplifies the configuration of decisioning strategies that simultaneously apply to multiple types of audiences, for example, Devices, Households, and Subscribers. The Embedded strategy shape eliminates the need to switch between various classes to create a substrategy for each audience type that you want to target. Now, you can perform all configuration tasks on a single strategy canvas.

For more information, see Strategy components – Embedded strategy and Multilevel decisioning strategies.

Quicker approach for reusing processes in a stage

You can now reuse processes more quickly in a stage when you define the life cycle for a case type. Reusing processes saves time and makes it easier to define processes for a stage instead of creating new ones. You can also reuse processes faster when you add parallel processes to a stage.

For more information, see Quick access for reusing processes in a stage.

Improved user management for new applications

You can now invite users to join your team when you run the New Application wizard. By managing user credentials and roles during application setup, you can start development immediately.

For more information, see Creating an application.

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

Custom mobile app assets file validation at upload

When you build a custom mobile app, and upload branding assets or custom modules within a compressed file, Pega^® Platform validates the file that you upload and displays confirmation and warning messages. For more information, see Uploading branding assets and custom modules.

New appearance of smart app banners

When you build a custom mobile app, you can use smart app banners to advertise your app. The look of these smart app banners has been modernized. Also, if you upload branding assets to customize the appearance of your custom mobile app, the smart app banners now display an icon that you upload as the main icon of your custom mobile app.

For more information, see Adding a banner for mobile app download.