Component type details and examples
These are the components that you can use to build trigger systems.
Event components
| Component Type | Description |
|---|---|
| Backward Inactivity | Listens for the occurrence of a specified event and then checks a specified prior time frame
to see whether another specified event has occurred. The Backward Inactivity component fires if the
specified prior event did not occur. Example: Fire when a customer makes use of the ATM after more than 1 month of not using any teller services. |
| Container Manipulator | Add and delete data in Container components and perform operations on this data. Can trigger
positive events or negative events. Example: When the dollar amount of product a customer purchased in one month exceeds $200 (value in the container), offer a discount. |
| Forward Inactivity | Listens for the occurrence of an event and then waits a specified time to see whether or not
another event occurs. The Forward Inactivity component fires when the time period expires without
the occurrence of the event it for which it was listening. Example: Fire when a web-trade customer, who usually trades once a month, does not trade for two consecutive months. |
| Pattern (Match All, Counter, Weighted Counter) | Listens for the occurrence of specified events. Fires if the events occur within a specified
time frame. In addition, you can configure a Pattern component to fire a negative event if the
pattern is no longer matched within the specified time frame. Example: Fire when customer uses his credit card four times a month during a three month period. |
| Simple | Fires if specified conditions based on transaction attributes are satisfied. A Simple is the only component type that is activated by incoming transactions and not by an event produced by another component. This is why every trigger system requires at least one Simple component as its starting point. Example: Fire when a customer makes a credit card purchase over $5000 or an international phone call to Italy. |
Data components
| Component Type | Description |
|---|---|
| Boolean Expression | Evaluates data and returns True or False. |
| Container | Holds records from transactions or a profile, as specified by a Container Manipulator. Other
components can use this data in calculations and comparisons. Example: Save the total dollar amount of customer purchases in one month. |
| Date | Returns a date. Specifies date or date range. Often used in Simple components to specify
criteria that incoming transactions must meet. Example: A transaction that occurred on June 8, 2013. |
| Math | Returns a number. Specifies a mathematical formula that uses numeric data from one or more
data sources. Common usage includes the following.
Example: In a Math component, calculate 95% of the customer's available account balance, which is available in a Simple component. In a Boolean component, compare this number to credit card transactions, and if a credit card purchase is equal to the number produced by the Math component, fire a positive event that activates a downstream Action component. |
| Select | A database query that returns a specified set of records drawn from a Container or another Select component. Other components can use this data in calculations and comparisons. |
| Trend | Detects 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. There are three trend components: Trend, Spike, Exceeded Standard Deviation
(ESD). Trend components never fire on their own. They are used internally by Action or Container Manipulator components. You can configure an Action or Container Manipulator component to fire when a Trend Component evaluates to true. For example, the average rolling monthly balance has been increasing or decreasing by 10% over the last three months. |
The Action component
The Action component is the only one that writes to the outcome destination. When you configure an Action component, you define the data that is written to the outcome destination when all the criteria specified in the components that the Action component depends upon are met. Outcomes can be written to a database table or can be sent to a customized program via a Web Service connector.