Action usage

Input action is used to get input from the user. The input can be free or constraint with regular expression. You can use the action by drag and drop it from the actions menu (or simply by clicking on it). Inside its configuration menu, you can choose the parameter name that will be used to save the user input, validation regex expression if needed, and the connection to the next action:

Note: Our system supports predefined regular expressions, just type # inside "Validation regex expression" and I menu will appear with supported types which are:

• Phone number
• Email
• License Pallete

There is a drop list near the validation regex expression which is regex expression flags that affect the search as next:

• i: with this flag, the search is case-insensitive: no difference between A and a.
• g: with this flag, the search looks for all matches, without it – only the first match is returned
• m: multiline mode (covered in the chapter Multiline mode of anchors ^ $, flag "m" of https://javascript.info/ website)
• s: enables “dotall” mode, which allows a dot. to match newline character \n (covered in the chapter Character classes of https://javascript.info/ website).
• u: enables full Unicode support. The flag enables the correct processing of surrogate pairs. More about that in the chapter Unicode: flag "u" and class \p{...} of https://javascript.info/ website.
• y: “Sticky” mode: searching at the exact position in the text (covered in the chapter Sticky flag "y", searching at the position of https://javascript.info/)

If you would like to learn more about flags, see What is Regular Expression (Regex)?.

Behavior

Input action is designed to get text input from the user, so in case of a connect message, it will do nothing. In other cases it will behave with the next step in order:

1. Will check a user input match in global keywords, and if the match exists it will continue the flow to the connection specified in that global keyword.
2. Will check the user input and if there is no regular expression or the input matches the regular expression constraint it will save that input and continue the flow, in case of regular 
3. Will fallback if the input didn't match the regular expression constraint, in that case, if the fallback count defined it will keep sending the local or global error message until the count is finished then it will continue the flow to the fallback connection.

Defining a delay for this action will delay continuing to the next action (Either if its the input action connection or the fallback connection).