Activities may be linked to one another in the Interaction Designer workspace. By default, the entire output of a parent activity (typically a set of customer or prospect records) serves as the input to any child activities.
However, it is possible to configure a child activity such that it only targets a subset of the parent’s output. In summary, the ways in which a child may be configured in this way are:
•Where the parent provides multiple segments (discrete blocks of data), by configuring a child activity to only apply to the data in a subset of the segments.
•By configuring the child to only apply to data with matching metadata attribute values.
•By specifying that the child will act only upon records that match specific fulfillment states – be these provided by a channel (such as ‘Clicked Through’ from an email channel), or custom fulfillment states (for example, ‘Application Accepted’).
Note that full details of how these configuration activities are carried out are provided elsewhere, as are details of the concepts themselves.
When explicit inputs are defined at an activity, an input indicator is displayed to the left hand side of and just above the incoming connector.
An input indicator is not displayed when no explicit inputs are defined.
The following activity input indicator text is displayed for each of the following scenarios:
•Child configured to act upon subset of parent’s segments:
o Single parent segment selected:
§ ‘[ParentSegmentName]’
o Multiple parent segments selected:
§ ‘[ParentSegmentName] + [n]’ (where [n] is the number of additional segments selected)
•Child configured to act upon only records with specific metadata attribute values:
o When one or more values are specified for one metadata attribute:
§ ‘[MetaAttributeName]’
o When one or more values are specified for more than one metadata attribute:
§ ‘[MetaAttributeName] + [n]’ (where [n] is the number of additional metadata attributes for which values are specified)
•Child configured to act upon subset of parent segments, and only records with specific metadata attribute values:
o Stipulations shown on two separate lines, with parent segments first
•Child configured to only act upon records with one or more fulfillment state(s):
o If channel fulfillment state(s):
§ ‘[ChannelName]’ displayed on top line
§ Fulfillment states selected for channel, shown on second line (‘[StateName]’; ‘[StateName] + [n]’ (where [n] is the number of additional states selected)
Hovering over an input indicator displays a tooltip, the text of which is dependent on the scenario in question:
•Parent segment(s) specified:
'Inputs:
[Segment1]
[Segment2]
[...]'
•Metadata filter(s) specified:
'Metadata filters:
[MetadataAttribute1]
[MetadataAttribute2]
[...]'
•Parent segments and metadata filters specified
Inputs followed by Metadata filters
•Fulfillment state(s) specified
'Fulfillment state inputs:
[Channel]
[State1]
[State2]
[...]'