Scripts written in the legacy scripting language represent a single or
composite expression from the built-in and custom functions. By using a Function action
within a test, you can enter an expression that refers to a specific function by name
(built-in or custom). These expressions can be used in the Function or Decision action
types, and within individual message fields to provide dynamic content. More complex
expressions can refer to several functions by using a nested bracket syntax, which is
familiar to programmers, for example: eq(5,abs(5.2)), which is the same as
eq(5,5.2) and evaluates to "false."
Project custom functions are available to all users of a project. If a
project is cloned, the same files and functions from the original project is available in
the cloned project.
Function names are case-sensitive.
You can use the result of one function as the input to another. For
example, the result of an XPath query can be used as a comparison against the result of a
database query.
When you are using functions, any string objects must be enclosed in
straight quotes (for example, "My text").
Strings that are passed to functions can be enclosed in quotation marks. Strings that
are not enclosed in quotation marks cannot contain spaces or internal quotation marks.
However, you can create tags to represent quotation marks or spaces and use them in
unquoted strings, as in the following
example:
<img%%space%%src=%%quote%%picture.jpg%%quote%%%%space%%\>
The function receives this string in the following
form:
<img src="picture.jpg" \>