Types of Nintex Forms
This topic describes the types of Nintex Forms. While each form can be created in the Forms designer, the forms are created and stored in slightly different contexts, which has effects access to some data sources and where the form definition in the form XML is stored in SharePoint.
There are five main type of forms:
In addition to these type of forms you may encounter the global form type, which is the name given to the list form or content type list form XML on export.
List Form
A list form is a stand-alone form that is associated with a SharePoint list and independent of a Nintex Workflow. List forms are most commonly used for data collection that depends on a specific SharePoint item or document, such as an inventory or list of contacts.
When a list form is added to a list it will open automatically when an item is added to the list.
List forms are rendered within the context of the SharePoint list or document library to which it is associated. List forms are stored as form XML in the SharePoint list. The list form can be bound to columns in the list. The form description is stored as form XML in the list and has a ContentType and listId.
The list form can be accessed through the Forms designer, through the SharePoint API, or the Nintex Forms Web Service.
You can use list forms independently of Nintex Workflow. You can also have the list kick-off a workflow by having the workflow start when a new item is created in the list. When an item is created for the list, the user will use the Nintex Form, and when they save their form data, a new record will be created in the list, and kick off the workflow.
Document Library Form
The document library form is also a stand-alone form associated with a SharePoint list or document library. Using SharePoint Designer, a site administrator can add multiple Nintex Forms to a single list. Each items is distinguished by the ContentType
The document library form is stored in the list just like a list form. When you wish to retrieve the form via the RESTful API, you will need to specify the ContentType in addition to the listId.
Start Form
The start form is created in the context of a Nintex Workflow and associated with the start action. The form has access to workflow variables. The form description is stored as form XML in the Nintex Workflow action definition (.nwf). The form description can be accessed through the Workflow Designer, through the SharePoint API through the Workflow description, or the Nintex Workflow Web Service.
Task Form
A task form is a form that is associated with a NintexWorkflow action. It commonly used to collect workflow-specific data such as approvals, and review comments.
Task forms can also be associated with the workflow start as a start form which will open when the workflow starts. Task forms have access to variables in the workflow context.
Task forms (and start forms) are stored as form XML in the Workflow XML.
The start form is created in the context of a Nintex Workflow and associated with the start action. The form has access to workflow variables. The form description is stored as form XML in the Nintex Workflow action definition (.nwf). The form description can be accessed through the Workflow Designer, through the SharePoint API through the Workflow description, or the Nintex Workflow Web Service.
Form Template
Form templates are form descriptions files loaded to manage device layouts page in Nintex Forms Management. Form template layouts can be selected from the Forms designer.
A template is a saved form definition that is used to apply default settings for newly created form layouts. A form export file (.xml) is used to import templates. A template will be added for each layout in the exported form definition. For example: A form is exported with a Default layout, iPad layout and a Smart Phone layout. Whenever one of these three layouts are created, the template settings will be applied. Templates are available at the site level.