Strategy components
Enrichment

Components in this category add information and value to strategies.

Set Property

• Set property components enrich data by adding information to other components, allowing you to define personalized data to be delivered when issuing a decision. Personalized data often depends on segmentation components and includes definitions used in the process of creating and controlling a personalized interaction, such as:
  • Instructions for the channel system or product/service propositions to be offered including customized scripts, incentives, bonus, channel, revenue and cost information.
  • Probabilities of subsequent behavior or other variable element.
  These components enrich data through the Target tab. Use the Target tab to add comments and set strategy properties for which you want to define default values. Comments can be defined through adding rows, setting the Action drop-down to Comment and entering the appropriate comment. Properties can be set through adding rows, setting the Action drop-down to Set and mapping the properties in Target and Source.
  Set property components created with releases previous to PRPC 6.2 SP2 DSM Edition supported overriding property values in the strategy through the Overrides tab, but this functionality has been removed since then. Strategy components defined in this way will show the configuration in the Overrides tab if there was a previous configuration, but no changes can be made.

Data Join

Data join components import data in an embedded page, named page or strategy component and map strategy properties to properties from the page or component. Data join components enrich data through the Join and the Properties Mapping tabs. These type of component can be used to join lists of values; for example, a data join component that has one or more components as source and uses the results of another strategy component to define the join conditions.

In the Join tab of this component:

• Use the Type drop-down to select the type of data: Pages or Component.

• In the Name field:
  • When joining data with a page, select the page.
  • When joining data with a strategy component, select the name of the component.
• The Class field displays the class context.
• The criteria to match data is defined as one or more conditions in the Join when all conditions are met section. This is a value pair between properties in the data join component and, depending on what you selected in the Select Type field, properties in the page or strategy component. You can determine the amount of data to include in the Exclude source component results check box, an option that, if enabled, results in performing an inner join operation.

Decision Parameters

Decision parameters components import the data defined in decision parameters instances.

• In the Decision Parameters tab, select the decision parameters instance. The when conditions allow you to match properties brought by the decision parameters instance and properties defined by the decision parameters component. The condition can be provided by a property or an expression.

• In the Properties Mapping tab, configure the mapping settings. The Define Mapping check box turns on/off implicit mapping by name. Automatically Mapped Properties lists the properties that are subject to this type of mapping. For decision parameters properties that do not have an implicit counterpart among the strategy results (that is, name matching does not apply), you can explicitly map them by using the Enable additional mapping option.

Strategy design