New shape on the strategy canvas
Valid from Pega Version 7.4
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
Valid from Pega Version 7.4
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
HBase data set type becomes resumable
Valid from Pega Version 7.4
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.
Naming pattern changed for file data sets
Valid from Pega Version 8.6.3
File data sets are used to import from and export data to a file repository. In case of data export, prior to version 8.6.3, the first file exported had the same file name that was provided by the user in the data set, and any subsequent file exported to the repository had a unique identifier appended to it. Starting in Pega Platform version 8.6.3, each file has a unique identifier, automatically generated based on the data flow node, thread ID, and timestamp.
Upgrade impact
If your process to consume output files expects files with a specific name, it may not be able to process the resulting files correctly.
What steps are required to update the application to be compatible with this change?
If you have configured the process before updating to Pega Platform version 8.6.3, but the exported files are no longer recognized by downstream processing logic after the upgrade, ensure that the downstream tool is configured to recognize the files by a pattern rather than the full name. For example, when referring to files exported to the repository, use the * character to indicate a pattern instead of using the full file name. For example, use Export*.csv to refer to the files.