Number Matching
N2FE Flow Operation - Number Matching
The NumberMatching
node takes a value from a source user buffer and performs a match against a specified set of match rule patterns.
The NumberMatching
operation has three exits.
The exits are:
- Number Found (the source user buffer value matched a match rule pattern).
- Number not Found (the source user buffer value did not match any match rule pattern).
- Number is Undefined (the source user buffer value is not defined).
Config Parameters
The NumberMatching
operation config
attributes are as follows.
Parameter | Type | Description |
---|---|---|
match_rules |
List of Strings | [Required] The match_rules parameter is a List of Strings that defines a list of match patterns to use when comparing the value stored in the source user buffer.The expected format of each match rule is the same as an NCC search pattern. |
source_buffer |
User Buffer | [Required] This must be the Name of a User Buffer (e.g. user.postcode or user.input ) from which the value to compare will be retrieved.See the notes on Buffer Names in the Flow Introduction documentation. The GUI may allow free-form entry for the user buffer name, or may restrict it to pre-determined values. |
Example Operation
Here is an example NumberMatching
operation in JSON representation.
{
"id": 5,
"type": "NumberMatching",
"base_node": 1,
"config": {
"match_rules": [
"1??",
"2??",
"3??"
]
"source_buffer": "user.follow_me"
},
"exits": [ 8, 9, 10 ]
}
Exits
There are always exactly three exits for an NumberMatching
operation.
Exit Index | Name | Description |
---|---|---|
1 | Number Found | [Required] This exit is followed if the value in the source user buffer matched a defined rule pattern. |
2 | Number not Found | [Required] This exit is followed if the value in the source user buffer did not match any defined match rule pattern. |
3 | Number is Undefined | [Required] This exit is followed if the source user buffer did not contain a value. |