Triggers

The trigger will be set up as seen in the image below.

Summary of Steps:

1. From the Trigger Events pop-up, click Add Raw Trigger.
2. Select the Feed Name for the trigger to monitor.
3. Select an attribute/aggregation to filter by.
4. Set values of the chosen attribute/aggregation in condition.
5. Click the ellipses (…) on the condition group to add another condition.

From the Trigger Events pop-up seen in the image below, click Add Raw Condition.

The raw trigger will be displayed as in the image below where the user can select either a Feed Name or a Data Model for the trigger to filter by. A Feed is an organized set of attributes or aggregates. A Data Model is an abstract model that can be applied to different feeds.

Clicking on Select feed will display the list of feed names to choose from, as seen in the image below. Each of these feeds contain sets of related attributes and aggregations. Select Feed Name as Transaction Based Triggers which represents the real-time credit card feed.

Choosing this feed will display a condition group where the attribute or aggregation to be filtered by can be selected, as seen in the image below.

A list of attributes and aggregations available for that feed will be displayed, as seen in the image below. Select transactionType. In our example, both attributes are expected to be present in Credit Card Transaction feed, otherwise another feed can be selected here.

Please select cardDescription and transactionCountry, which is equal to "Freshers" and "TW" respectively, in this example. The cardDescription attribute will be displayed, as seen in the image below.

The operator will be displayed, as seen in the image below. Type the value that represents Freshers cards in the space provided, enclosed in double quotes as this is a String. The appropriate error condition will be displayed that can be used as a hint to what type of value is expected like a string, integer (number) or boolean (true/false).

Click the ellipses on the condition group to add another condition within that group, as seen in the image below. In our example, both attributes are expected to be present in Credit Card Transaction feed, otherwise another feed can be selected above.

A new raw trigger condition will be displayed, as seen in the image below. Specify transactionCountryCode values. This will be kept as an ALL condition group.

The final set of trigger conditions can be seen in the image below.

The second condition filters whether the transaction has occurred abroad or not. The transactionCountryCode refers to the country where the transaction occurred. The code for Taiwan is TW, therefore a code not equal to TW refers to a transaction abroad. Note that the value for this condition is enclosed in double quotes.