...
| Code Block |
|---|
|
{
"confidence": 97,
"+and": [
{
"+rule": ["L:no-reply@contract.fit"],
"where_to_search": {
"search_in": ["email_from"],
"limits": [[0,10], [-20]]}
},
{
"-rule": ["L:\\+32\\d{9}"],
"where_to_search": {
"search_in": ["email_body"]
}
}
]
} |
...
...
This is a list of strings that are contained in the granularity. Here we don’t look at the original text, but the lemmatised version of the text.
| Note |
|---|
IMPORTANT: Regex is quite a bit more efficient than the and/or operators. Try to use regexes as much as possible. |
| Info |
|---|
Note that when using different operators the where_to_search will be passed down. If on a lower level one is found, that one will be used. This way you can: |
Variables
...
| Code Block |
|---|
|
{
"no_reply": {
"variables": {
"var1": ["L:\\+32\\d{9}"]
},
"rules": [
{
"confidence": 97,
"+and": [
{
"+rule": ["L:no-reply@contract.fit"],
"where_to_search": {
"search_in": ["email_from"],
"limits": [[0,10], [-20]]}
},
{
"-rule": ["D:var1"],
"where_to_search": {
"search_in": ["email_body"]
}
}
]
}
]
}
} |
Lemma
This is a list of strings that are contained in the granularity. Here we don’t look at the original text, but the lemmatised version of the text.
| Note |
|---|
IMPORTANT: Regex is quite a bit more efficient than the and/or operators. Try to use regexes as much as possible. |
| Info |
|---|
Note that when using different operators the where_to_search will be passed down. If on a lower level one is found, that one will be used. This way you can: |
FAQ
| Expand |
|---|
| title | How can I only look in the email subject for my regex? |
|---|
|
By adding the option where_to_search::search_in to your rule. An example field would look like this: | Code Block |
|---|
| "rules": [
{
"confidence": 97,
"+rule": ["L:no-reply@contract.fit"]
"where_to_search":
{
"search_in": ["email_subject"]
}
}
] |
|
...