Application development tools for state tables

You can use either of the two different approaches to develop your state table applications:

Using the state table editor

Blueworx Voice Response includes an easy-to-use state table editor for creating and editing voice applications. This editor can represent the logic in a graphical Icon view or a text-based List view, and is accessed from the Blueworx Voice Response user interface. It is described in State tables.

Using an ASCII editor

You can use an ASCII editor instead of the Blueworx Voice Response user interface to create the code for state tables, prompts, and 3270 server scripts. ASCII-format code can be stored in an external code repository, imported into Blueworx Voice Response, and then debugged using the Blueworx Voice Response windows. You can use a command-line interface instead of the window menu option to import ASCII state tables and prompts, so you can schedule jobs to import automatically all the changed files from your code repository. User-specified version-control information can be retained, after importing files into Blueworx Voice Response.

You can define as read-only objects that are imported from ASCII source files, to prevent modification within Blueworx Voice Response. However, if you prefer, an imported state table, prompt, or script can be modified.

A state table, prompt, or script developed or modified using the Blueworx Voice Response user interface can be exported and then modified using your favorite editor. However, if you import an ASCII state table, and then export it again, the ASCII code generated by Blueworx Voice Response does not necessarily look the same as the ASCII file you originally imported. In other words, ‘round-tripping’ is not normally possible.