About trigger systems

To create your business logic, you configure sets of components called trigger systems. Some components send events that activate other components, while others perform operations on data and make the results available to other components.

A trigger system is a time-sensitive detection algorithm that detects relevant patterns over time in a customer’s behavior. Each trigger system solves a single detection problem. Multiple trigger systems can share components that hold saved data.

A trigger system produces Outcome data that is written to a database, to a web servlet, or to a queue.

For production, multiple trigger systems are collected into a single workspace, which you run to process your transaction data.

Trigger systems can be complex and sophisticated, but at a minimum every trigger system requires the following.

• A data source

  Data sources must include transaction data and can also include static customer profile data.

  Data source setup and requirements are described in the HCL® Opportunity Detect Administrator's Guide.

• A Simple component

  Detects discrete events in the stream of input data. A Simple component looks for specified criteria based on a single audience level in a single transaction data source.

• An Action component

  Writes Outcome data to a destination specified by the data source connector used for outcomes. This data is available for use by external systems, and can be used in HCL Campaign.

Trigger system development

A workspace can include multiple trigger systems, but it is a good practice during the development and test phase to use a different workspace for each trigger system. This makes it easier to:

• understand each piece of logic as you build it, and
• test and refine the outcomes.

When you have tested all of your trigger systems, you can then use component references to copy them to one workspace for production runs.