TeleFlow Variables
From TeleFlow
TeleFlow Variables are loosely defined and are processed according to their context. The format definition of the variable will determine what type of information the variable represents. For example, a TeleFlow Date is determined when it is stored as "YYYY/MM/DD". A TeleFlow Time is stored as "HH:MM:SS". Numeric and string values are treated accordingly.
Contents |
Variable Naming Rules
- A variable is denoted with an @ symbol
- A variable name must start with a letter or an underscore "_"
- Only letters (a...z, A...Z), numbers (0...9) and underscores ( _ ) can be used in variable names.
- A variable name may not contain spaces. If a variable name is more than one word, it must be separated with underscore (@my_string), or with capitalization (@myString)
- For variable names, TeleFlow is not case sensitive. It treats all variables as being in UPPER CASE, regardless of how they are referred to in the application.
System Variables
There are TeleFlow System Variables which provide information about the operating environment, and there are user defined variables
Formatting Variables
TeleFlow's variables can be placed together in strings in order to define a new value. The following constructs will help you build strings when other characters are included. This example includes multiple variables to create a unique file name:
- @dictationFile=Dictations\\dictation_U@{pU_ID}_C@{pCommand}_T@UNIX_TIME.wav
- The value created and stored in @dictationFile might look like:
Dictations\\dictation_U2_C19_T1213228616.048.wav
Accordingly:
- The curly braces { } are used to isolate variable names from other characters:
- @pU_ID (does not include the following underscore and C)
- @pCommand (does not include the following underscore and T)
- @UNIX_TIME, a system variable, is delimited with a period (.), which cannot be included in the variable name.
- In this case, the double backslashes are required for MySQL
Related Steps
Set Global Variable Step
Set Local Variable
Math
