Function is a set of operations and plugins that are put together as one-group to execute a specific sub process within the whole process. Functions are often utilized to improve design and maintenance efficiency when a specific process must be executed multiple times in one large process (bot).
Like Steps, Functions have a timeline on which you line-up your Operations and Plugins. In Functions, you can use all tools from the STU toolbox.
You can have a Call Function inside a function that calls for another function. However, Call Function is designed to prohibit “recursive” calls which means calling of the mother function from the daughter function which was originally called by the mother function.
When used in a function, Go To operation can only go to another operations inside the function.
Within one bot, all pre-defined and user-defined variables are shared among Steps and Functions.
Call Function operation gives you a feature to implement “conditional branching” depending on the success or failure of the function execution.
Here is how “Result Handler” works in the Call Function operation.
Function Error will be executed only when “AbortAsFunctionError” result is sent back from any one of the verification tools inside the function.
These verification tools will have an option to return “AboartAsFunctionError” only when they are deployed in a Function.
End Function will be executed for everything else (except when AbortAsError has happened in a Function – then the bot will stop)
How to set parameters.
|
|