You build expressions and configure incoming events and time spans when you work with several types of components. In addition, all component editors have a left panel where you configure or view basic attributes. Read this section to understand these commonly used component attributes.
Fields where you can enter a description of the component. Optional.
HCL® Opportunity Detect enables you to look for specified customer behaviors and patterns in your customer data. You define the transactions and patterns that Opportunity Detect looks for, and you specify the data that is written to the database or web servlet when those criteria are met.
The permissions assigned to users in Opportunity Detect determine what areas of the application they can access and the actions they can perform.
You build trigger systems in workspaces. This procedure provides the basic steps for setting up workspaces. Details on adding and using components are provided elsewhere in this guide.
There are three ways to add components to workspaces: by creating a component from the Component Palette, by copying a component within a workspace, and by using a component reference to share a component across workspaces.
You can create and run deployment configurations and view deployment and batch run history on the Workspaces page.
Opportunity Detect generates one outcome record for every set of transactions that meets the criteria specified in the trigger system.
Components are the basic building blocks for trigger systems in Opportunity Detect.
The Data Dependencies panel contains a read-only list of transaction data sources that are allowed and used in this component and the audience level associated with these data sources. The fields update as you configure a component.
The name and type of any components that use this component. Use this information when you want to make a change to a component, to see what other components might be affected by the change. Read only.
Fields where you can set a start and end date during which an event component is active. Optional.
Fields where you set a limit on how often an event component produces its event. Optional.
All event components except the Simple require an incoming event to activate them. The incoming event signals to the component that there is data for it to evaluate against its criteria.
Time spans are used throughout Opportunity Detect to specify time periods.
When you configure a calendar time span or an effective window, you use time constants and time units. Time constants, the starting points of time units, and the end points of irregular time units have specific definitions within Opportunity Detect.
A firing condition is required for Simple components and is optional for Action components. You can define an expression to serve as a firing condition. The expression can be an existing Boolean expression component, or you can define an inline expression that is available only within the component where it is defined.
Functions perform some additional processing on a record set returned by a Container or Select component. Functions allow you to apply commonly used database functions to the records.
The Expression Builder is used throughout Opportunity Detect to compare strings and numbers, perform math operations, and apply database functions.
In Opportunity Detect, you use regular expressions in two situations.
Expression components evaluate customer data and return a value that can be used by other components. You can create similar logic by using inline expressions within components, but creating an expression component for frequently used calculations allows you to re-use this logic.
Trigger systems in HCL® Opportunity Detect all have Simple components as their basic building block. Simple is the only component type that is triggered by incoming transactions in the transaction data feed, and not by an event produced by another component. This is why every trigger system requires at least one Simple component.
The purpose of an Action component is to send a notification that a specified behavior has occurred by writing data to a database or sending the data to a web service. Like all event components, an Action component fires and writes its outcome when it receives an incoming event from another event component.
Select components perform operations that are similar to the SQL SELECT database query with optional WHERE clauses. A Select component holds a set of records that you define, and on which you can perform further operations.
Container components store data that you define for a specified length of time. Container components depend on Container Manipulator components to feed them the data that they store.
You can use Pattern components to test whether one or more events for a given customer occur over a period of time. A Pattern component collects events that match its criteria and stores these events in the customer's state history. When the specified pattern of events is met, the pattern drops those events from state history and fires a positive event.
You use a Backward Inactivity component when you want to verify that some event did not occur within a specified period of time prior to an incoming event. You use a Forward Inactivity component to set a timer when it receives an incoming event, and optionally to specify another event that turns off the timer.
Trend components detect changes in activity measured over defined periods of time. Before you can create a trend component, your trigger system must include a Container or Select component that the trend can use as a data source.
An artificial transaction (ATX) is a system-generated event that you can use as an incoming event in an event component.
Components in a trigger system can be said to have ancestor and descendent relationships with each other. Ancestor and descendent relationships affect many aspects of component behavior.
You can share a component in multiple workspaces by using component references.
Use this procedure to delete components from workspaces in Opportunity Detect.
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.
You can set either a calendar or rolling time span in Forward Inactivity components.
You specify the calendar time span for the pattern using the Time Span section of the component editor.
You specify the rolling time span for the pattern using the Time Span section of the component editor.
Use this procedure to add components to workspaces from the Component Palette in Opportunity Detect.
Use this procedure to share a component across workspaces.
Use this procedure to add a component within a workspace by saving a copy of a component using a new name.
In the Workspace List, you can create, delete, and modify the basic properties of workspaces.
Use this procedure to run a workspace for test or production purposes.
Data source connectors enable the system to connect to the transaction, profile, lookup, State History, and Outcome data sources that you have defined. The types of data source connectors are described in this section.
When the Expanded Outcome data source connector is used for Outcome data, the system writes the data in a form that can be used by HCL® Campaign or an external system.
The Opportunity Detect engine can run batch files when it completes a run. You can use these files to issue different notifications for each successful and failed engine run.
On the Deployment tab of a workspace, you can create deployment configurations for workspaces, map data source connectors within the deployment configuration, deploy the configurations, stop and restart deployments, and view deployment history.
On the Batch Run tab, you can manage run parameters, run deployed workspaces, see the status of the most recent batch runs, and stop and start ongoing runs.
On the Batch History tab, you can see details about past runs, filtered by deployment and a date range.
Data source connectors can be mapped to different data sources in each deployment configuration, which provides flexibility for testing and ramp-up operations.
The input mode that you select determines what data source connectors are allowed for the data sources used in the workspace. The Input mode field is located on the Properties tab of a deployment configuration.
Use this procedure to create and deploy a deployment configuration.
The IsMemberOf (IMO) function provides an efficient method for identifying and acting on large quantities of lookup table data to determine which records contain a specified value.
Container components provide a way to create a data structure similar to a database table in your trigger systems. You use the Container to define the table that holds the data inserted by a Container Manipulator.
When a customer withdraws $10,000 from her account, you might want to determine whether she has made any other withdrawals larger than $5,000 within the past two months. For this, you would use a Backward Inactivity component.
By default, a Pattern fires a positive event when its criteria are met, but it does not fire a negative event when the aging out of an event creates a negative condition. However, you can configure the behavior to include negative events.
Pattern behavior options allow you to enable the pattern to fire a negative event (by default patterns fire only positive events). They also allow you to delay firing the negative event.
You use Container Manipulator components to add and delete data in Container components.
Help Center