This release of DASH revision 3.1 adds a number of changes and improvements to the initial 3.0 release.

Form structures have changed somewhat in 3.1 and a utility is available to automatically convert most of a DASH 3.0 form to a 3.1 version.

• XML structures are defined by a schema instead of a DTD.
• The data entry server is now controlled by a XML parameter file instead of a dash.properties file.
• A scheduler now handles call allocation for cati interviewing and web interviewing.
• Interviewer and supervisor logins allow access to the forms and viewing of the scheduler internal state.
• A web btrser based menu system allows execution of all utilities across a network from any btrser with access to the DASH server.

• Multiple language capability in forms is now implemented and all viewable elements may show the appropriate language if the language is switched.
• Text elements may now be laid out with the same flexibility as fields in table structures.
• Lists in forms may now be dynamically built to reflect client selected data.
• Lists may now be placed within a page element in the form.
• A help button is now available and may display a help page or an external help file.
• The button field may now be used to trigger Tcl logic or JavaScript.
• Graphic buttons may be used to replace the default text based buttons.
• A logo may be included in the button tr.
• Different language versions of buttons may be made available for language switching.
• A large number of property tags have been added to allow increased web client configurability.
• Many new Tcl commands have been added.

• All utilities may be run from a btrser menu interface as well as from the shell to allow automation.
• A built in form testing facility with no scheduler impact.
• Full forms or page subsets may be printed in HTML format.
• Marginals may be filtered by field selection, case selection or a logic condition. Marginals may be weighted. Marginals have numerous layout options added.
• Data load and dump procedures include complex filters to allow fine control of data import and export. Data may be appended to the form file or overlaid or added to existing cases.

• The integer field now allows negative integers.
• The web client message to the server was restricted to 1024 characters which meant extremely long data fields were truncated. The maximum message length is now 65000 characters.