In this information we usually assume
that you are using the graphical user interface to develop state tables.
Once you have gained some experience of state table development, or
if you are an experienced application programmer, you may prefer to
use an ASCII editor of your choice to create the code for state tables.
This is what you need to do if you choose to create your state
tables using an ASCII editor:
- In addition to the state table actions, include any programming
logic constructs in your state tables. These are described in ASCII state table statements.
- Create any prompt directories or servers that are referred to,
or state tables that are invoked, by the state table.
- Import the state table using the graphical interface,
described in Importing ASCII code into a state table. If the state
table does not validate at this point, make any necessary changes
and try importing again. Alternatively, you can use the DTst command
to import or export your state table. See The DTst command.
- Validate the state table, as described in the procedure for Defining state table properties.
- Make any necessary changes. If you need to modify the state table,
you may prefer to make your changes to the original ASCII file and
import it again, or you can make the changes using Blueworx Voice Response windows
and re-export the modified state table to an ASCII file, if you want
to keep the ASCII copy in step.
- Repeat from step 3 until the
state table validates with no errors.
Note:
- There are limits on the number of characters you can use for variable
and label names. For more information, see ID and name limitations.
- You cannot use any of the ASCII state table statements described
in this section (for
example, ON and DESCRIPTION) as
names of variables.
- If you want a character string to be treated as a variable, you
must declare it first, otherwise it is treated as a constant.
.