Outcome data in Opportunity Detect

Opportunity Detect generates one outcome record for every set of transactions that meets the criteria specified in the trigger system.

Outcome data can have different formats, depending on the data source connector that you use for your Outcomes when you run your trigger systems.

You assign data source connectors to tables, queues, or a web service when you create server groups. When you deploy a trigger system, you can change this default mapping in the deployment configuration.

How Outcome data is specified in trigger systems

Outcome data is specified in the Action component, in the Outcome panel. This panel has two fields:

Message, which holds a text string that you specify.
Additional information, which holds data captured using an inline expression. The inline expression can choose data from any data source or component that is available to the Action component.
This data can be a single value (scalar), or a row in a data record stored in a Container or Select component (tabular).

Types of data source connectors for Outcomes

For Outcome data, Opportunity Detect provides four types of data source connectors.

Outcome table: Used when you want Outcome data to be stored in database tables in the XML format used by previous versions of Opportunity Detect.
Expanded Outcome tables: Used when you want Outcome data to be stored in database tables in a form that external systems or HCL® Campaign can use more easily than the format provided by the Outcome connector.
Web Service: Used when your system is configured to use the Opportunity Detect web servlet for Outcome data, for real time operation. See the HCL Opportunity Detect Administrator's Guide for details about the Java classes that must be developed to use the Web Service data source connector.
Queue: Used when your system is configured to use a Queue connector for Outcome data, for real time operation. See the HCL Opportunity Detect Administrator's Guide for information on setting up a Queue data source connector.