Once the templates created, you can write a scenario. As said before, a scenario is a set of rules. You can create one or more rules in each scenario, and you can write one or multiple scenarios with the same type.
Create a scenario
The Rules
A rule of a scenario is composed of a name, a description, a clickable case “Active” that will activate the rule. It comport also two important part “WHEN” that will define the rule itself and the “THEN” that will define the actions that will ensue the success of the situation described by the rule.
To create a rule :
The "WHEN" part :
The “WHEN” will be where the rule is set. It response to a precise Grammar. An attribute system
is also in place so when you type “#” a list of all possible attributes will be displayed. You can add conditions with adding “AND” or “OR” after the first rule is written.
All the logic operators available are :
For a chain of character :
= (equal to)
!= (different from)
in (in the following statement)
not in (not in the following statement)
Please note you need to frame the chain of character with quotation mark " ".
For numbers :
= (equal to)
!= (different from)
< (less than)
> (greater than)
<= (less or equal to)
>= (greater or equal to)
in (in the following statement)
not in (not in the following statement)
For a boolean (a true or false statement) :
= (equal to)
!= (different from)
Please note for the IN and NOT IN you need to frame the following statement with parenthesis. You can add multiple data in these parenthesis, if you separate them by comma.
You can prioritize a statement by adding parenthesis around. If you use a AND and a OR, please prioritize a part. If you use multiple AND and OR you need to prioritize each part accordingly.
Example of valid rules :
#end_user_country in ('FRA', 'BE')
#authorisation_status = 'FAILURE' or (#transaction_amount > 100000 and #context = 'TRANSACTION_RISKY' )
#transaction_amount > 100000 and ( #authorisation_status = 'FAILURE' or #context = 'TRANSACTION_RISKY' )
((#transaction_amount > 100000 and #context = 'TRANSACTION_RISKY') or ( #authorisation_status = 'FAILURE' and #transaction_amount < 100000 )) and (#card_product_type = 'Consumer')
Before saving the rule, you need to test the rule with the adequate button. It will verify the rule follow the grammar used for the rules and if the rule will work once activated. You cannot save a rule without a fully working rule and a correct grammar.
An example of correct rule :
The "THEN" part :
The “THEN” w
ill be where you can choose the actions triggered by the rules. These actions can require the use of templates once the rules activated. You can only have access to templates that correspond of the type of template needed (SMS, Email, Hook) and the type of scenario you are working on (Dispute , Transaction, Installment Payment).
An example of choice of Templates :
Collective Rules
Some rules are predefined for all the actors and will be applied to you. You can verify this in your protected area in your ‘Notification’ tab. You can unsubscribe to some of these rules by using the clickable case.
