The differences between Forms and Actions.

When you create a template, the first decision you need to make is, what type of template.

There are 2 types of templates used in Damstra Forms: 

 - Forms
 - Actions

The template type used determines:
 - Which register the records are created/stored in 
 - The functionality associated with the records (for example, you can filter the Actions register to create a Punch List of action items;  you can add Approvals sections to Forms).

Below is a description of the differences between these, and examples of scenarios in which you would use each. 

Form

This is a general use template type, and has the most functionality available. Most of the templates you create will be Forms. 

When you create a new Form, you'll be provided with the following system fields:

Action

Actions are simple templates designed for items that require follow-up - for example, logging workshop items, corrective actions or non-conformance items that are noted during inspections. 

You can prompt field users to create Actions based on responses to Question fields in Forms by clicking on the Question's cog icon, and configuring Settings > Attach to Question with the Action template and auto-popup options.

In the above, when a field user selects Yes as the answer to this Question in the inspection form, a new Defect action will pop up for them to complete, pre-filled with the Short Description "Service needed". Alternatively, they could attach an existing Defect.

You can filter the Action register to show a list of Actions (for example: all Actions with Owner = Me) and click Create Punch List to get a PDF list of those items.

Note: you can not add tables to Action templates.

When you create a new Action, you'll be provided with the following system fields: