vTask XML Data Structure


vTask Studio stores scripts in XML files. The "VXM" extension stands for "vTask XML," and is fully XML-compliant.
The basic structure of the file is:

    <vTask>
      <step>
          <data-tags>
      </step>
      ...unlimited number of additional steps
    </vTask>


The spacing and indentation of the <data-tags> is preserved during file saves. In other words, if you prefer a single tab indentation, or 4-spaces indentation, the same spacing will be used upon each save.

The full list of all VXM tags is listed below. Only a few are used for each command. The actual data tags used depend on the specific command.

    <step>
        <action>
        <text>
        <options>
        <value1>
        <value2>
        <value3>
        <value4>
        <value5>
        <value6>
        <value7>
        <value8>
        <data>
        <timeout>
        <output>
        <onfail>
        <comment>
        <custom>
    </step>


You can access the internal data fields by using the {step[1].comment} (and similar) system variables.


 
The <custom> XML tag
One data tag exists for special use. The "<custom>" XML field can be used for any user-defined purpose. It was added to allow customized information (user data) to be stored in the XML file. It can be used in the script as data, for step identity, or simply for documentation.

The <custom> XML tag includes the following features:

• Always preserved during file open/saves, even when manually modified externally
• Not touched or otherwise modified by vTask in any way (it is "off-limits" to vTask)
• The "Find" feature will include this field during searches (but not Replace)
• Accessible to your script at any time via the {step[1].custom} data field
• Guaranteed to be supported in the future, regardless of upgrades/internal data changes

It is limited to 256 bytes (native vTask data fields like <text> and <comment> are unlimited). You can store data, text, numbers, binary bytes, Excel formulas, or whatever you need. This information is available in the script via the {step[1].custom} system variable.

For example, you can store a number value in the <custom> field, and use it with normal Excel formulas:



As an advanced feature, the <custom> field is not shown by default in the Properties box or in the main grid. To view and edit it, select the "Edit <custom> tag in Properties" checkbox in the Options screen:





This data field is also available in the main grid, and can be edited there:



The default display color is purple, and can be changed in the Tools => Options => Colors dialog: