Published Release Notes

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.

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.

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.

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.

Improved Back button support in custom mobile apps for Android

In a custom mobile app for Android, you can press the Back hardware button to go back, instead of exiting the app. Custom mobile apps now function in the same way as native Android apps. For example, you can close a dialog box, dismiss an overlay, or collapse an expanded section by pressing the Back hardware button. On the home screen, pressing the Back hardware button displays a confirmation message before you can exit the app.

Improvements to support Kibana log viewing

Pega® Cloud resolved a known infrastructure error that prevented customers in AP-southeast-2 region from properly viewing their log messages in Kibana.

Pega Cloud introduced this enhancement as of QI 2018.

View status of custom search indexes

Custom search indexes are special purpose indexes that are created and managed outside of Pega Platform™. You can view the status of custom search indexes on the Search landing page to see whether they are complete. This information is useful for troubleshooting and can help you determine whether to rebuild the index.

For more information, see Checking search index status.