Published Release Notes

Layout groups and design templates

On the Design tab of the Section form in Designer Studio, you can use a layout group to display closely related information by using accordion, menu, stacked, or tab navigation elements. You can then create a templated region that is based on the layout group. For example, you can use this type of region to enable users to add, reorder, or remove tabs from screens at run time in Pega^® Express.

For more information, see Creating a templated region based on a layout group and Creating a templated region based on a layout group.

Actions for included sections

On the Design tab of the Section form in Designer Studio, you can include a section inside another section. To enhance reuse possibilities, you can also add an action to an included section. For example, you might specify an action set that automatically displays a smart tip when a user hovers over the included section in one case, but specify a different action set for the same included section in another form or even in another application.

For more information, see Adding actions to included sections.

Specify styles at run time in Pega Express

At run time in Pega^® Express, you can now apply styling to many controls. Styling options vary from one control to another. For example, when you style a Dropdown control, you can specify text color, background fill and color, and border width and color. When you style controls directly in Pega Express, rather than switching to Designer Studio to modify the application skin, you can save development time.

For more information, see Styling controls at run time in Pega Express.

Configure the window size at run time in event strategies

You can now configure an Event Strategy rule to dynamically define the window size at run time by using a property value of the incoming record. To configure the window shape for dynamic size setting, you can use any property from the inheritance path that is available to the event strategy. This enhancement provides greater flexibility for strategy designers and broadens the scope of business scenarios in which event strategies can be applied.

For more information, see Event Strategy rule form - Completing the Event Strategy tab and Dynamic window size behavior.

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

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.

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.