|
|
|
|
|
Assuming the name used in the External Function Call is fname and the application is called appname, the function should be placed in a file, fname.t, in the application directory, which is /att/trans/sb/appname for Script Builder applications or /lt/trans/sc/appname for IVR Designer applications. External functions placed in this directory are considered to be part of the application and are backed up and restored as part of the application.
Since the main script file is called appname.t, you cannot have an external function with the same name. The fname.t file should have a label called L_ _fname, which is where the function begins execution when called from a TAS application. Labels used in external functions must not conflict with labels used in other functions or in the application. To avoid conflicts, all labels should start with the same L_ _fname label designated as the entry point.
External functions can also be placed in the external function library. Once in this library, these external functions are available to any application on the system. The library is a directory, /vs/bin/ag/lib, of .t files, one per function. Avoid changing other files in the directory, because many of them are used directly by the system and altering them causes the system to fail. Also, avoid overwriting any files or using names that are used by other functions. File names that begin with an underscore (_) are either earlier versions or routines that are used internally by the system.
External functions located in the library are not backed up with the application. Therefore, they should be backed up separately.
External functions must use the following naming conventions:
