Overview
Rules containing this step, must have a sister rule with a Create Future Events step to create the timers
This is the only rule that does not start with a Real Time Input Step
When the timer expires, a following action can be implemented in the rule
The Process Future Event task can add many entries for the same Key
To ensure that the latest entry is valid, a filter condition should immediately follow the task
Plugin Configuration
General
Within the General tab:
The following settings can be configured:
Setting | Description |
|---|---|
Server names(s) | The name of the cache server(s) you are using. If the rule is running in DDE then this is automatically be populated and the value will be ignored. |
KeySpace | Tables exist in Keyspace (similar to a database). If the rule is running in DDE then this is automatically be populated with the client name within DDE and the value will be ignored. |
Table | The name of the table which will be created in Cassandra. If left blank this will be the same as the key field name. |
Key | The field that contains the unique key (primary key) which identify items in the cache. e.g. Customer ID or Order ID |
Event loop count limit | Set the maximum amount of times that the same record (based on the Key) can be processed. For example you may want limit the amount of abandoned emails being sent for 1 individual to 3 for example. If an event is processed more than this number of times then the data is sent to the error output. The rule should therefore have an error handling step to cater for events that exceed the event loop limit. e.g.  If an error handling step is not configured, any event exceeding the limit will be discarded. |