Component type details and examples
These are the components that you can use to build trigger systems.
Event components
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.
Forward Inactivity
Listens for the occurrence of a specified event and then waits a specified time to see whether or not another specified event occurs. The Forward Inactivity component fires when the time period expires without the occurrence of the event it for which it was waiting.
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)
Fires if specified 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
Data components
Component Type
Description
Boolean Expression
Evaluates data and returns True or False.
The Action component
The Action component is the only one that writes to the outcome table. When you configure an Action component, you define the data that is written to the outcome table when all the criteria specified in the components that the Action component depends upon are met.
Copyright IBM Corporation 2013. All Rights Reserved.