Instead of coding solutions as apps, we rely on Vortex, a generic workflow engine and a small set of control files that define the required appearance and behaviour. One control file lists the variables you want to collect, one lists the groups, types, or species your variables pertain to, one contains the multiple choice answers for the drop-down lists (spinners), and one file – to rule them all – contains the workflows with instructions defining the user interface, the data entry flow, verification rules to apply, and page layout to use.
Defaults and Historical data can be imported to support for instance laying-out GIS Objects on a map, or pre-filling certain values to guide the user. Images used can either be preloaded or referenced by URL (image data can also be cached from URL links for Off-Grid use.)
Once Field Pad had been initialized, the bundle can be used without Internet connection.
Vortex runs the workflows, renders the forms and verifies the entered data. Pictures can also be included as part of the data collection.
When done, data can be exported in one of several formats.
Vortex Workflows
Let's have a closer look at the workflows that are executed by Vortex. Consider the following picture that illustrates a simple workflow. In the workflow, each of the blocks correspond to one step in our XML language. Block 1 starts the workflow, block 2 defines the page type, block 3 defines a text to be dispalyed, etc.
