By default each unique form stores its data in its own normalized table called EFTable_{x} with {x} is the form template unique ID. In addition there is also a database view called EFView_{x} which is a replication of the EFTable_{x} except the column names in the view are the field elements names instead of the unique 43 characters ID in the table. Each data column in the table represent a data entry field in the form. In Enterprise Forms, a data entry field are those field elements of the following types
field elements that either marked as NotADatafield or belongs to one of the following types are not created with the database table
| • | Label (except for those with default value set) |
In addition to the field columns system also stores additional metadata related to the current state of the workflow. These include
| • | formid – this is the form template unique id generally the same as the {x} in the table/view name |
| • | instance_id – this is the unique id of the submitted form instance. With each new form submitted the system creates a new instance_id and this id exists and is used throughout it workflow lifecycle to distinguish between each new form record |
| • | hist_id – this is the unique id representing the current state of the workflow for a particular instance |
The three ids combined to represent the unique record and state of a submitted form for any particular state in its workflow lifecycle.
As an example, say we have a form with 3 simple data entry fields, FirstName, LastName, and DateOfBirth the result EFView_{x} will have the following columns
The table/view can be accessed like any other standard database table.
