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. There is a command-line interface for importing ASCII state tables and prompts, so you can schedule jobs to import all changed files from your code repository automatically. User-specified version control information can be retained, after importing files into Blueworx Voice Response.
Objects imported from ASCII source files can be defined as read-only, to prevent modification within Blueworx Voice Response. However, if you prefer, an imported state table, prompt, or script can be modified within Blueworx Voice Response.
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, you should be aware that, if you import an ASCII state table and then export it again, the ASCII code generated by Blueworx Voice Response will not necessarily look the same as the ASCII file you originally imported. In other words, "round tripping" is not necessarily possible.
After you have learned the Blueworx Voice Response programming language, you can create new applications that reuse modules from existing applications quickly and easily.