Published Release Notes

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.

Ability to delete the Mobile channel interface

When you build a Pega^® Platform application, you can create a mobile app for your users. When you no longer need the mobile app, you can now delete an existing Mobile channel interface, just like any other channel that is available from the Channels and interfaces landing page.

For more information, see Channels and interfaces.

Ability to annotate case attachments

Pega^® Platform application users can now add annotations to images that are attached to cases. For example, users can draw around an area of an image to highlight a faulty element of the device. Users can annotate all images, except for signature images or attachments that are stored in Pega Cloud or other external data stores. The annotated case attachments replace the original ones.

For more information, see Case attachment annotations.

New application document types capture features and user stories

Pega® Platform adds two new application document types based on features and stories:

• Use product overview documents to socialize the application development plan and progress.
• Use gap analysis documents to identify the gaps between the application and your needs to clarify which customizations to build.

For more information, see Real-time agile application document types.

HBase data set type becomes resumable

HBase data set has been enhanced to be resumable. As a result, data flow runs that reference the HBase data set as their primary data source are now resumable. You can pause and resume such data flow runs.

For more information, see the Resumability of data flow runs section in Data flow run updates.