Nintex Forms uses a license file (.nlf) for server licensing. A single license file is used to store information about all servers in a farm that are licensed for Nintex Forms.
To import a license:
Installing Nintex Live
Activating Nintex Forms
Manage database
Getting started with the form designer
Please contact our sales team for licensing advice at sales@nintex.com.
To activate Nintex Forms Prerequisites Feature in a site collection
After a short delay, the page will refresh and the status will become Active.
Note: Nintex Workflow must be installed and configured prior to activating this feature.
To activate Nintex Forms for Nintex Workflow in a site collection:
After a short delay, the page will refresh and the status will become Active.
To activate Nintex Forms for SharePoint List Forms in a site collection:
After a short delay, the page will refresh and the status will become Active.
To activate Nintex Live Forms in a site collection:
After a short delay, the page will refresh and the status will become Active.
Getting started with the form designer
Live Forms settings
Importing and exporting forms
Configuring the Start Site Workflow Webpart
To activate Nintex Forms on a Web Application, the Nintex Forms solution must be installed and deployed on the Web Application.
To activate the Nintex Forms solution on the Web Application:
After a short delay, the page will refresh and the status will become Active.
The Manage device layouts page allows the addition, removal and configuration of layouts that are targeted to devices. In addition, a template can be associated with a device layout. Refer to Associating templates to device layouts for more information.
This page displays a summary view of the configured layout options targeted to the device.
To add a new device layout:
The Device Details page is displayed as follows:
To delete a device layout:
Note: There is no warning to confirm deletion at this stage.
Associating templates to device layouts
Form and Layout settings
Designing a form for a mobile device
Getting started with the form 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.
Once a template has been uploaded, the device templates that were found within the form export file will be listed below the Browse button.
To deactivate a template for one or more specific device layout(s), deselect the Use Template setting in Manage device layouts.
Note: Only one template may be applied for the farm. Uploading a template file will clear all existing templates and apply only the layouts found in the most recent file uploaded.
Importing and exporting forms
Getting started with the form designer
Form and Layout settings
Manage device layouts
The Manage Form Controls page lists all of the installed controls that are available for use when designing a form.
For more information on the functionality of the individual controls please refer to the Control help topics.
Control Settings
Controls In Use
Connecting Controls to fields or variables
Linked Controls
The Manage database page can be used to configure the database that will store Nintex Forms configuration and application settings.
The Nintex Forms installation requires a single database to store the server specific configuration settings. A new database or an existing database can be used.
Use of the default database server and database name is recommended for most cases. Refer to the administrator's guide for advanced scenarios where specifying database information is required.
Use of Windows authentication is strongly recommended. To use SQL authentication, specify the credentials which will be used to connect to the database.
The database may be associated with a failover server that is used in with SQL Server database mirroring.
Manage device layouts
Licensing settings
Manage form controls
Live Forms settings
View Live forms
Use the Live Forms settings page to enable or disable the ability to publish forms to Nintex Live, and allow or disallow anonymous user access.
Note: Ensure that the Nintex Live Framework and the certificates required to enable connectivity to Nintex Live have been installed.
If the "Install Nintex Live" option was not selected during Nintex Forms installation, manually install and deploy the “nintexlivecore.wsp”.
Note: A database for Nintex Forms must be provisioned before Nintex Live Forms can be enabled. Refer to Manage database for more information.
Note: When Nintex Live Forms is disabled, forms already published to Nintex Live will remain active. Live Form submissions will be held in the Nintex Live message queue until retrieved or cleared*. Re-enabling Nintex Live Forms will retrieve and process all stored form submissions.
To disable all forms published to Nintex Live, please see View Live forms for more information.
*Nintex will endeavour to hold and deliver all undelivered forms, however, periodic clearing of stale content may be necessary. Please contact Nintex if you have special requirements for holding content or clearing held content.
Installing Nintex Live
View Live forms
Web Application activation settings
Live Settings
Saving and publishing forms
Manage database
Nintex Live is a hosted service provided by Nintex.
The Nintex Live Framework and certificates are required to enable connectivity to Nintex Live.
The Nintex Live components must be installed to enable the Nintex Live features of Nintex Forms. These features allow form designers to publish designated forms to Nintex Live. Nintex Live Forms can be accessed by internet users, either anonymously or via 3rd party authentication providers.
The following steps are required to manually install the Nintex Live Framework and certificates if the "Install Nintex Live" option was not selected during Nintex Forms 2013 installation. The SharePoint PowerShell Command Prompt must be used to install the components.
To launch the SharePoint PowerShell Command Prompt:
In the SharePoint PowerShell Command Prompt, type:
CD "C:\Program Files\Nintex\Nintex Forms 2013"
Note: The default installation path is "C:\Program Files\Nintex\Nintex Forms 2013", replace with actual location if installed to a different location.
Add-SPSolution -LiteralPath "C:\Program Files\Nintex\Nintex Forms 2013\NintexLiveCore.wsp"
Install-SPSolution -Identity "1ddec2be-094d-4a9b-b9e1-fdca27b07646" -GACDeployment -Force
Note: Wait for the solution to be deployed. Check the status of the solution deployment in the Central Administration > System Settings > Manage farm solutions page.
Install-SPFeature -SolutionId "1ddec2be-094d-4a9b-b9e1-fdca27b07646" -AllExistingFeatures -Force
Remove-PSSnapin Microsoft.SharePoint.PowerShell
Add-PSSnapin Microsoft.SharePoint.PowerShell
Install-LiveService
In the SharePoint PowerShell Command Prompt type:
CD "C:\Program Files\Nintex\Nintex Forms 2013\Certs"
Note: The default installation path is "C:\Program Files\Nintex\Nintex Forms 2013", replace with actual location if installed to a different location.
.\CertificateUpload.ps1
Live Forms settings
View Live forms
Activating Nintex Forms
The View Live forms page displays list forms and workflow start forms that are currently published to Nintex Live. Forms can be viewed or removed.
Use the Select form type drop down to display the different form types available.
Note: Removing the form does not uncheck the "Publish to Nintex Live" option in the Live Settings. If the form is published again, it will be republished to Nintex Live.
Note: If the form is removed from Nintex Live and then republished, the Live Form URL will revert to the original URL when first published.
Live Settings
Saving and publishing forms
Installing Nintex Live
View Live forms
Live Forms settings
Enable or disable users of the Nintex Mobile App to connect to forms and tasks through the Nintex Live framework.
The page is displayed as follows:
Enable individual users of the Nintex Mobile App to connect to forms and tasks though the Nintex Live framework or disable individual users from connecting.
Related Topics
Nintex SharePoint Feature | ID |
---|---|
NintexFormsAdminWeb | 70f4f7da-4fb4-4e30-ba1a-a733efb2e1ac |
NintexFormsFarm | ada0910e-a663-4db4-a19c-d8a097317b87 |
NintexFormsListSite | 202afc3c-7384-4700-978d-6da3d3cce192 |
NintexFormsLiveSite | 23fce797-ac15-4451-b8da-cf8ac6de6912 |
NintexFormsSitePrerequisites | 716f0ee9-e2b0-41f0-a73c-47ed73f135de |
NintexFormsWebApplication | 0cdf436f-61b0-43d2-b250-4360f0353b63 |
NintexFormsWorkflowSite | ac8addc7-7252-4136-8dcb-9887a277ae2c |
NintexLiveAdminLinks | 29e9a673-31a4-46a3-b0d2-d8e1db1dbd92 |
Nintex Forms 2013 is available in the following editions.
Please contact our sales team if you need advice at sales@nintex.com.
Valid Software Assurance is required in order to update to the latest version of Nintex Forms.
Selection | Description |
Enable Forms Based Authentication for Nintex Mobile | When enabled, authenticates Nintex Mobile users through a web application sign-in page. The following options are available.
|
Set Nintex Mobile Token Expiry | Number of days before each user-specific encrypted token expires. |
The Button control can be used to initiate an action, such as submitting a form or initiating a custom JavaScript.
Note: The Button control is not supported in Nintex Mobile. The control is not needed in Nintex Mobile because the Save and Cancel buttons are generated individually by platform.
Section | Selection | Description |
General | Name | The name of the control. The name is used for comparison validation and other control references. |
Button action | This selects the function of the button. Select JavaScript to specify custom functionality. |
|
| Button type | Select the display type for the button. |
| Button label | The text to display on the button. |
Appearance | Visible | Hide or show control at runtime. |
| Horizontal width | The width of the control as a %, pixel or point value. |
| Vertical height | The height of the control as a %, pixel or point value. |
Formatting | CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings). |
| Border | Draws a line along the select border of the control. |
| Border Style | The style of the border. |
| Border Width (Pixels) | The width of the border in pixels. |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. |
Ribbon | Show on Ribbon | Show this button on the Ribbon toolbar (if available) in addition to the form. |
| Ribbon icon URL | If shown on the Ribbon toolbar, specify the URL of the icon (32x32px) to use. |
| Ribbon button order | Determines the order in which buttons will appear on the ribbon toolbar. |
| Ribbon button group name | The name of the Ribbon toolbar group to display the button. |
Advanced | Visible when in view mode | Hide or show the control in view mode. If Yes is selected:
|
| Causes validation | Apply validation for JavaScript button types. |
| Client click | The JavaScript to execute when the user clicks the button. |
| Connected to | The field to bind the input control to. If a selection is made in the List Columns:
|
| Confirmation message | When the user clicks on the button during runtime, they will be prompted with this message prior to the buttons functionality being processed. |
| Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form length and position of other controls accordingly. |
Getting started with the form designer
Controls In Use
Control Settings
Connecting Controls to fields or variables
Shortcut keys
Inserting reference fields
Control Properties Ribbon
The Choice control can be used to make a single or multiple selection on a form.
Section | Selection | Description | Nintex Mobile |
General | Name | The name of the control. The name is used for comparison validation and other control references. |
Yes |
| Connected to | The field to bind the input control to. | Yes |
| Display format | Select the type of choice control to display. (Option buttons / Checkbox / List / Drop down) | Yes |
| Choices | Enter the choices to be displayed. | Yes |
| Default value source | Select whether the default value will be inherited from the column definition or whether another specified value will be used. | Yes |
| Default value | Set a default value for the control. If a control is connected to a SharePoint list column, enter the value or expression value to override the Choice default specified in the SharePoint column. | Yes |
| Render as buttons | When Display Format is set to Options Buttons (also known as "radio buttons" this allows the control to be rendered as styled buttons which can appear like tabs. By using this option with Rules a basic tab-like interface can be built on your form. | No |
| Arrange choices | Items can be arranged across then down or down then across. | Yes |
| Number of columns | Number of columns to use to display the specified choices. | Yes |
| Column alignment | Align the choices in fixed columns or allow them to float. | Yes |
| Allow "Fill-in" choices | Allows the user at runtime to specify a choice other than those presented. | No |
Appearance | Visible | Hide or show the control at runtime. | Yes |
| Enabled | Enable the control to receive user input when the form is in input mode. | Yes |
Formatting | Control CSS class | The CSS class to apply to the inner elements of the control. | No |
| CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form and Layout settings). | No |
| Border | Draws a line along the select border of the control. | No |
| Border Style | The style of the border. | No |
| Border Width (Pixels) | The width of the border in pixels. | No |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. | No |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. | No |
Validation | Required | The form will not submit unless this control is completed correctly. If Yes is selected:
|
Yes |
| Data Type | The data type to convert to during validation. | No |
| Use custom validation | Enables the value entered into the control to be validated by a JavaScript function. If Yes is selected:
|
No |
Advanced | Help text | Help text that will be displayed to the user as a tooltip to guide the completion of the form. | No |
| Control Mode | Force control to be in Edit mode, Display mode, or set to Auto. | No |
| Store Client ID in JavaScript variable | A JavaScript variable will be created that references the Client ID of this control. If Yes is selected:
|
No |
| Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form length and position of other controls accordingly. | No |
Getting started with the form designer
Control Settings
Controls In Use
Connecting Controls to fields or variables
Shortcut keys
Yes-No Control
Inserting reference fields
Control Properties Ribbon
Use Rich Text to display formatted text, pictures, hyperlinks and tables on a form.
Note: The Rich Text control is not supported in Nintex Mobile.
Section | Selection | Description |
General | (unlabeled) | To enter or edit content, click in the text area. |
| Name | The name of the control. The name is used for comparison validation and other control references. |
Appearance | Visible | Hide or show the control at runtime. |
Formatting | CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings). |
| Border | Draws a line along the selected border of the control. |
| Border Style | The style of the border. |
| Border Width (Pixels) | The width of the border in pixels. |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. |
Advanced | Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form length and position of other controls accordingly. |
Getting started with the form designer
Control Settings
Controls In Use
Inserting reference fields
Shortcut keys
Multi Line Textbox
Single Line Textbox
Inserting reference fields
The Hyperlink control can be used to enter a hyperlink URL and display text.
Getting started with the form designer
Control Settings
Controls In Use
Connecting Controls to fields or variables
Shortcut keys
Inserting reference fields
Control Properties Ribbon
The Image control can be used to display an image on a form.
Getting started with the form designer
Control Settings
Controls In Use
Label
Shortcut keys
Inserting reference fields
Control Properties Ribbon
The Label control can be used to place text anywhere on the form. Labels are often placed next to other controls to describe the associated control.
Section | Selection | Description | Nintex Mobile |
General | (unlabeled) | To enter or edit content, click in the text area. |
Yes |
| Name | The name of the control. The name is used for comparison validation and other control references. | Yes |
Associated control | Select the control that this label describes. This is used for web browser accessibility. Note: By default, when a Label is associated to a bound control (a control that is associated to a column or workflow variable), the default value of the label will reflect the name of the column or workflow variable the control is bound to. |
Yes | |
Appearance | Visible | Hide or show the control at runtime. | Yes |
Formatting | CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings. | No |
| Border | Draws a line along the select border of the control. | No |
| Border Style | The style of the border. | No |
| Border Width (Pixels) | The width of the border in pixels. | No |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. | No |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. | No |
Advanced | Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form length and position of other controls accordingly. | No |
Getting started with the form designer
Control Settings
Controls In Use
Inserting reference fields
Shortcut keys
Image
Control Properties Ribbon
The Date/ Time control can be used to either enter a date and time or select a date from a calendar display.
Section | Selection | Description | Nintex Mobile |
General | Name | The name of the control. The name is used for comparison validation and other control references. |
Yes |
| Connected to | The field to bind the input control to. | Yes |
| Default value | Set a default value for the display. This value will only be used if a default value has not been specified in the column or variable in the Connected to setting. If Selected date option:
|
Yes |
| Date only | Show the date only without the time. | Yes |
Appearance | Visible | Hide or show the control at runtime. | Yes |
| Enabled | Enable the control to receive user input when the form is in input mode. | Yes |
Formatting | Control CSS class | The CSS class to apply to the inner input control. | No |
| CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings). | No |
| Border | Draws a line along the select border of the control. | No |
| Border Style | The style of the border. | No |
| Border Width (Pixels) | The width of the border in pixels. | No |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. | No |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. | No |
Validation | Required | The form will not submit unless this control is completed correctly. If Yes is selected:
|
Yes |
| Compare to | Enables the value entered into the control to be validated against a specified value, or the current value in another control. If Control is selected:
If Value is selected:
|
Yes |
| Use range validation | Enables the value entered into the control to be validated against a specified maximum and minimum value. If Yes is selected:
|
Yes |
| Use a regular expression | Enables the value entered into the control to be validated against a regular expression. If Yes is selected:
|
No |
| Use custom validation | Enables the value entered into the control to be validated by a JavaScript function. If Yes is selected:
|
No |
Advanced | Help text | Help text that will be displayed to the user as a tooltip to guide the completion of the form. | No |
| Control Mode | Force control to be in Edit mode, Display mode, or set to Auto. | No |
| Convert empty string to null | Convert to a null value if the control contains an empty string. | No |
| Null display text | If the bound value is null, this text will be displayed instead. | No |
| String format | The string format to apply to the displayed value. | No |
| Store Client ID in JavaScript variable | A JavaScript variable will be created that references the Client ID of this control. If Yes is selected:
|
No |
| Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form length and position of other controls accordingly. | No |
Getting started with the form designer
Control Settings
Controls In Use
Connecting Controls to fields or variables
Shortcut keys
Control Properties Ribbon
The Border control can be used to display a line along one or more borders of the control.
Note: Several settings allow Yes, No or Expression to be selected. Expression allows a formula to be constructed from reference tokens and functions. The expression must resolve to a Yes/No value at runtime to be valid. If the expression does not resolve to a Yes/No value it will revert to the default.
Section | Selection | Description | Nintex Mobile |
General | Name | The name of the control. The name is used for comparison validation and other control references. |
Yes |
Appearance | Visible | Hide or show the control at runtime. | Yes |
Formatting | CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings) | No |
| Border | Draws a line along the selected border of the control. | Yes |
| Border Style | The style of the border. | Yes |
| Border Width (Pixels) | The width of the border in pixels. | Yes |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. Note: When used in Nintex Mobile layouts, the color must be a HEX or RGB value. |
Yes |
Getting started with the form designer
Control Settings
Controls In Use
Shortcut keys
Control Properties Ribbon
The List Item control can be used to display an item from a SharePoint list.
Note: The List Item control is not supported in Nintex Mobile.
Getting started with the form designer
Control Settings
Controls In Use
List View
List Attachment
List Lookup
Shortcut keys
Inserting reference fields
Control Properties Ribbon
Section | Selection | Description | Nintex Mobile |
General | Name | The name of the control. This name is used for comparison validation and other control settings. |
Yes |
| ID connected to | The column to bind the item ID of the returned lookup value to. Note: The column names specified in the ID Connected to field, must be of the type "Single line of text". | Yes |
| Text connected to | The column to bind the text returned from the lookup to. Note: When a List Lookup control is used, two pieces of data are returned: the ID of the item selected in the lookup and the text of the item selected in the lookup. Each of these can be bound to a List Column in the current list. The column names specified in the Text Connected to field, must be of the type "Single line of text". Note: If you will require Nintex Workflow to act on a returned list item, it will require the ID to refer to the list item. |
Yes |
| Source SharePoint site | The ID or the URL of the SharePoint site that contains the source list. This list can be anywhere within the web application. The site picker will only show sites within the current site collection, however, other sites can be entered as a server relative URL manually. | Yes |
| Source List | The list name or ID of the source SharePoint list. The lists available will dynamically be populated based on the specified site. If the system cannot access the site, the list name will need to be specified manually as an expression. | Yes |
| Source view | The SharePoint view to source the items from. | Yes |
| List column name | The name of the column to show in the lookup control. | Yes |
| Allow multiple values | Allows the user to select multiple values in the control. | Yes |
Appearance | Visible | Hide or show the control at runtime. | Yes |
| Enabled | Enable the control to receive user input at runtime. | Yes |
| Display format | The type of control to render. Available options in single select mode are: "Drop down list" and "Option Buttons", while in multi select mode, you can continue to use the SharePoint List Lookup Control (Default) or checkboxes or a list box similar to that available to the Choice control. | Yes |
| Use custom "Please select" text | Indicates whether the control will use custom text for the first item in the drop down list. | Yes |
Filtering | Filter available selections | Filter the selections in the Lookup by another control on the page or by a specific value. If By a controls value is selected:
If By a specified value is selected:
|
Yes |
| Action when no filter applied | Values to be shown when there is no value applied to the filter; where nothing is selected in the “filtered by control” or there is no valid specified filter value. | Yes |
Formatting | Control CSS class | The CSS class to apply to the inner input control. | No |
| CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings). | No |
| Border | Draws a line along the select border of the control. | No |
| Border Style | The style of the border. | No |
| Border Width (Pixels) | The width of the border in pixels. | No |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. | No |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. | No |
Validation | Required | The form will not submit unless this control is completed correctly. | Yes |
| Use custom validation | Enables custom JavaScript validation for the control. If Yes is selected:
|
No |
Advanced | Help text | Help text that will be displayed to the user as a tooltip to guide the completion of the form. | No |
| Control Mode | Force control to be in Edit mode, Display mode, or set to Auto. | No |
| Prepend ID to value | Select Yes to include the item ID number in front of the value. | No |
| Store Client ID in JavaScript variable | A JavaScript Variable will be created that references the Client ID of this control. If Yes is selected:
|
No |
| Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form length and position of other controls accordingly. | No |
Getting started with the form designer
Control Settings
Controls In Use
Connecting Controls to fields or variables
List Attachment
List Item
List View
Shortcut keys
Inserting reference fields
Control Properties Ribbon
The Multi Line Textbox control allows users to enter plain text on the form.
As with other controls the Multi Line Textbox inherits properties and settings from the field it is connected to. One property not visible in the Control Settings dialog is SharePoint's ability to show the previous history of the field. When enabled in the column settings, this will render at runtime as per the existing SharePoint functionality. We however will take up some of the space allocated to the control to display this history. The control will not grow as more history is collected.
Section | Selection | Description | Nintex Mobile |
General | Name | The name of the control. The name is used for comparison validation and other control references. |
Yes |
| Connected to | The field to bind the input control to. | Yes |
| Default value | Set a default value for the control. This value will only be used if a default value has not been specified in the column or variable selected in the Connected to setting. | Yes |
| Rich text | Allow rich text format to be entered. If Yes is selected:
|
Yes |
Appearance | Visible | Hide or show the control at runtime. | Yes |
| Enabled | Enable the control to receive user input when the form is in input mode. | Yes |
Formatting | Control CSS class | The CSS class to apply to the inner elements of the control. | No |
| CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings refer to (Form and Layout settings). | No |
| Border | Draws a line along the select border of the control. | No |
| Border Style | The style of the border. | No |
| Border Width (Pixels) | The width of the border in pixels. | No |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. | No |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. | No |
Validation | Required | The form will not submit unless this control is completed correctly. If Yes is selected:
|
Yes |
| Use custom validation | Enables the value entered into the control to be validated by a JavaScript function. If Yes is selected:
|
No |
Advanced | Help text | Help text that will be displayed to the user as a tooltip to guide the completion of the form. | No |
| Control Mode | Force control to be in Edit mode, Display mode, or set to Auto. | No |
| Convert empty string to null | Convert to a null value if the control contains an empty string. | No |
| Null display text | If the bound value is null, this text will be displayed instead. | No |
| Store Client ID in JavaScript variable | A JavaScript variable will be created that references the Client ID of this control. If Yes is selected:
|
No |
| Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form length and position of other controls accordingly. | No |
Getting started with the form designer
Control Settings
Controls In Use
Connecting Controls to fields or variables
Single Line Textbox
Rich Text
Shortcut keys
Inserting reference fields
Control Properties Ribbon
The Page Viewer control can be used to display a page on a form. The page viewer control works as an iframe and allows a view of a page or document to be included within the control.
Note: Some mobile devices and security settings may not support the display of a page from another website within a Nintex Form.
Getting started with the form designer
Control Settings
Controls In Use
Shortcut keys
Inserting reference fields
Control Properties Ribbon
The Panel control can be used to group controls together and optionally display a label and a border around the group.
To group controls together:
Note: In design mode, controls grouped within a Panel control can be moved around the form canvas collectively.
Getting started with the form designer
Control Settings
Controls In Use
Shortcut keys
Inserting reference fields
Control Properties Ribbon
The People control allows users to browse and select users from the SharePoint profile database.
Section | Selection | Description | Nintex Mobile |
General | Name | The name of the control. The name is used for comparison validation and other control references. |
Yes |
| Connected to | The field to bind the input control to. | Yes |
| Default value source | Only available when connected to a column, this option allows you to override the connected field's default with your own default expression. | Yes |
| Default value | Set a default value for the control. This value will only be used if a default value has not been specified in the column or variable selected in the Connected to setting or Default Value Source has been set to "Expression". | Yes |
| Multiple selections | Only available when connected to columns of certain data types. Allow multiple people to be selected. | Yes |
Appearance | Visible | Hide or show the control in runtime. | Yes |
| Enabled | Enable the control to receive user input when the form is in input mode. | Yes |
Formatting | Control CSS class | The CSS class to apply to the inner elements of the control. | No |
| CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings. | No |
| Border | Draws a line along the select border of the control. | No |
| Border Style | The style of the border. | No |
| Border Width (Pixels) | The width of the border in pixels. | No |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. | No |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. | No |
Validation | Required | The form will not submit unless this control is completed correctly. If Yes is selected:
|
Yes |
| Compare To | Enables the value entered into the control to be validated against a specified value or the current value in another control. If Control is selected:
If Value is selected:
|
No |
| Use custom validation | Enables the value entered into the control to be validated by a JavaScript function. If Yes is selected:
|
No |
Advanced | Entities to include | Only available when not connected to a column. The available user entity types that can be specified. | Yes |
| Maximum entities | The maximum number of users/ groups that can be selected if multiple selection is allowed. | Yes |
| SharePoint group | Filter the available entities by a specific SharePoint group. | Yes |
| Help text | Help text that will be displayed to the user as a tooltip to guide the completion of the form. | No |
| Control Mode | Force control to be in Edit mode, Display mode, or set to Auto. | No |
| Store Client ID in JavaScript variable | A JavaScript variable will be created that references the Client ID of this control. If Yes is selected:
|
No |
| Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form length and position of other controls accordingly. | No |
Getting started with the form designer
Control Settings
Controls In Use
Connecting Controls to fields or variables
Shortcut keys
Inserting reference fields
Control Properties Ribbon
The Single Line Textbox control allows users to enter plain text on a form.
Section | Selection | Description | Nintex Mobile |
General | Name | The name of the control. The name is used for comparison validation and other control references. |
Yes |
| Connected to | The field to bind the input control to. | Yes |
| Default value source | Only available when connected, allows you to override the connected fields default with your own default expression. | Yes |
| Default value | Set a default value for the control. The value will only be used if a default value has not been specified in the column or variable selected in the Connected to setting or Default Value Source has been set to "Expression". | Yes |
| Data Type | Only available when not connected. The data type to convert to during validation. | Yes |
Appearance | Visible | Hide or show the control at runtime. | Yes |
| Enabled | Enable the control to receive user input when the form is in input mode. | Yes |
Formatting | Control CSS class | The CSS class to apply to the inner elements of the control. | No |
| CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form and Layout settings. | No |
| Border | Draws a line along the select border of the control. | No |
| Border Style | The style of the border. | No |
| Border Width (Pixels) | The width of the border in pixels. | No |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. | No |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. | No |
Validation | Required | The form will not submit unless this control is completed correctly. If Yes is selected:
|
Yes |
| Compare To | Enables the value entered into the control to be validated against a specified value, or the current value in another control. If Control is selected:
If Value is selected:
|
Yes |
| Use range validation | Enables the value entered into the control to be validated against a specified maximum and minimum value. If Yes is selected:
|
Yes |
| Use a regular expression | Enables the value entered into the control to be validated against a regular expression. If Yes is selected:
|
Yes |
| Use custom validation | Enables the value entered into the control to be validated by a JavaScript function. If Yes is selected:
E.g. The property should be ClientValidate when the following function is added to the custom JavaScript in the form. function ClientValidate(source, arguments) { if (arguments.Value % 2 == 0){ arguments.IsValid = true; } else { arguments.IsValid = false; } }
|
Yes |
Advanced | Max length | Only available when not connected. The maximum length of the text that can be entered. | Yes |
| Password | Hide the password text with asterisks. | Yes |
| Help text | Help text that will be displayed to the user as a tooltip to guide the completion of the form. | No |
| Control Mode | Force control to be in Edit mode, Display mode, or set to Auto. | No |
| Convert empty string to null | Convert to a null value if the control contains an empty string. | No |
| Null display text | If the bound value is null, this text will be displayed instead. | No |
| String format | The string format to apply to the value. The string format will be determined by the type of data specified by the control. When it is a number the following can be used http://msdn.microsoft.com/en-us/library/0c899ak8.aspx, and http://msdn.microsoft.com/en-us/library/dwhawy9k.aspx. For other types see http://msdn.microsoft.com/en-us/library/26etazsy.aspx | No |
| Store Client ID in JavaScript variable | A JavaScript variable will be created that references the Client ID of this control. If Yes is selected:
|
No |
| Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form length and position of other controls accordingly. | No |
| Enable barcode scanning | Displays a button next to the control for scanning barcodes. Available in supported Nintex Mobile apps only. Select one of the following options. |
Yes |
Getting started with the form designer
Control Settings
Connecting Controls to fields or variables
Controls In Use
Shortcut keys
Rich Text
Multi Line Textbox
Inserting reference fields
Control Properties Ribbon
The Yes /No control allows users to check or uncheck a box to show that an item has been selected.
Section | Selection | Description | Nintex Mobile |
General | Name | The name of the control. The name is used for comparison validation and other control references. |
Yes |
| Connected to | The field to bind the input control to. | Yes |
| Text | The text to display next to the checkbox. | Yes |
| Default value source | Only available when connected to a column, this option allows you to override the connected field's default with your own default expression. | Yes |
| Default value | Set a default value for the control. If a control is connected to a SharePoint list column, use an expression value to override the Yes/No default specified in the SharePoint column. | Yes |
Appearance | Visible | Hide or show the control at runtime. | Yes |
| Enabled | Enable the control to receive the user input when the form is in input mode. | Yes |
Formatting | Control CSS class | The CSS class to apply to the inner elements of the control. | No |
| CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings). | No |
| Border | Draws a line along the selected border of the control. | No |
| Border Style | The style of the border. | No |
| Border Width (Pixels) | The width of the border in pixels. | No |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. | No |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. | No |
Validation | Required to be checked | The form will not submit unless this control is completed correctly. If Yes is selected:
|
Yes |
| Use custom validation | Enables the value entered into the control to be validated by a JavaScript function. If Yes is selected:
|
No |
Advanced | Help text | Help text that will be displayed to user as a tooltip to guide completion of the form. | No |
| Control Mode | Force control to be in Edit mode, Display mode, or set to Auto. | No |
| Store Client ID in JavaScript variable | A JavaScript variable will be created that references the Client ID of this control. If Yes is selected:
|
No |
| Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form length and position of other controls accordingly. | No |
Getting started with the form designer
Control Settings
Controls In Use
Connecting Controls to fields or variables
Choice Control
Inserting reference fields
Control Properties Ribbon
The Workflow Diagram control can be used to display a Nintex Workflow on a form.
Note: The Nintex workflow diagram control will only appear if Nintex Workflow has been installed and configured.
Note: The Workflow Diagram control is not supported in Nintex Mobile.
Section | Selection | Description |
General | Load from context | Display the workflow diagram based on the context of the form. When No is selected, displays additional fields. Note: Using this control on a start form will load a preview for the current workflow, a task form will show the status of the current task's workflow and a list form will show the state of the current running workflow (if there are multiple workflows running, SharePoint will look for the first workflow for that list item) or the first completed workflow. For more information on manually configuring the workflow diagram to display, refer to manual configuration scenarios. |
| Workflow Instance ID | The ID of a workflow instance. |
| Workflow name | The name of the workflow to display. |
| SharePoint List | The ID or name of the list if required. |
| List Item ID | The ID of the list item if required. |
Appearance | Visible | Hide or show the control at runtime. |
Formatting | CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings). |
| Border | Draws a line along the selected border of the control. |
| Border Style | The style of the border. |
| Border Width (Pixels) | The width of the border in pixels. |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. |
Advanced | Displays the control at runtime if the workflow cannot be found. | Show control at runtime if workflow not found. |
| Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form size and position of other controls accordingly. |
To display a diagram for a workflow on a list item (will look for the first workflow for the list item), specify the following:
To display a diagram for a specific running/completed workflow on a list item, specify the following:
To display a diagram for a site workflow, specify the following:
To display a diagram for a specific running / completed site workflow, specify the following:
Getting started with the form designer
Control Settings
Controls In Use
Inserting reference fields
Control Properties Ribbon
The List View control can be used to display a SharePoint List and optionally specify the List view to display.
Note: The External Data Column control is not supported in Nintex Mobile.
Selection | Field | Description |
General | Source SharePoint site | The URL or GUID of the SharePoint site the list is in. |
| List | The ID or name of the list. |
| View Name | The name of the view in the list that is displayed. If not specified, the default view will be displayed. |
Appearance | Visible | Hide or show the control at runtime. |
Filtering | Filter listed items | Filter the listed items by another control on the page, a specific value or custom query. |
Formatting | Control CSS class | The CSS class to apply to the inner elements of the control. |
| CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings. For more information, see Form and Layout settings. |
| Border | Draws a line along the selected border of the control. |
| Border Style | The style of the border. |
| Border Width (Pixels) | The width of the border in pixels. |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. |
Advanced | Lookup column filtering | The type of filtering for the lookup column. Select one of the following options.
|
Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form length and position of other controls accordingly. |
Getting started with the form designer
Control Settings
Controls In Use
List Attachment
List Item
List Lookup
Shortcut keys
Inserting reference fields
Control Properties Ribbon
The Attachments control allows users to attach files to the SharePoint list item that the form is currently adding or editing. For list forms it is the list item of the form. For task forms it will be the attachments for the task list item, not the list item the workflow is running on.
Note: If the browser being used does not support browsing the file system and selecting attachments, the 'browse' button will be disabled.
Section | Selection | Description | Nintex Mobile |
General | Name | The name of the control. The name is used for comparison validation and other control references. | Yes |
| Default control |
|
Yes |
Appearance | Visible | Hide or show the control at runtime. | Yes |
Formatting | CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings). | No |
| Border | Draws a line along the select border of the control. | No |
| Border Style | The style of the border. | No |
| Border Width (Pixels) | The width of the border in pixels. | No |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. | No |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. | No |
Validation | Minimum attachments | The number of attachments required for form submission. Note: When a value is specified for this field, a red asterisk appears in the published form, to the right of the label associated with this control. |
Yes |
| Minimum attachments error message | The text of the error message displayed if form is submitted without the required number of attachments. Example: "Résumé file must be attached." Nintex Mobile displays the following error message by default for this validation item. “You have not met the minimum number of required files.” |
Yes |
| Maximum attachment setting |
|
Yes |
| Maximum attachments | The highest number of attachments allowed for form submission. Note: This field is displayed only when you select Custom for Maximum attachments setting. Nintex Mobile displays the following error message by default for this validation item. “You have exceeded the maximum allowed number of files.” |
Yes |
| Allowed file formats (enter each format on its own line) | The file extensions validated at the time of attachment. Enter each file extension (format) on its own line. Example: doc Note: Separate from the form-specific file formats specified here, the SharePoint server may block file formats (file types). Nintex Mobile displays the following error message for any attached file type that is blocked by the SharePoint server. “The selected file type is blocked by the server. Select a different file type.” |
Yes |
| Disallowed file format error message | The text of the error message displayed if an attempted file attachment fails validation according to Allowed file formats. Nintex Mobile displays the following error message by default for this validation item. “The selected file type is not allowed for this form. Select a different file type.” |
Yes |
Getting started with the form designer
Control Settings
Controls In Use
List Item
List View
List Lookup
Shortcut keys
Inserting reference fields
Control Properties Ribbon
The Repeating Section is a control that can contain a set of other controls, and allows a user of the form to insert multiple instances (rows) of the set as required. A typical use is an expenses form where each row is an expense item.
The following controls are supported within repeating sections:
Note: When added to a Repeating Section control, child controls are connected to the Repeating Section control and thus cannot be connected to SharePoint columns or fields.
Section | Selection | Description | Nintex Mobile |
General | Name | The name of the control. The name is used for comparison validation and other control references. |
Yes |
| Connected to | The field to bind the input control to. | Yes |
| Text for add row icon | The text for add row item. | Yes |
| Default rows | The default number of rows to be displayed. | Yes |
| Minimum rows | The minimum number of rows to be displayed. | Yes |
| Maximum rows | The maximum number of rows to be displayed. | Yes |
Appearance | Visible | Hide or show the control at runtime. | Yes |
| Prevent add/delete in new/edit mode | Hides the add/delete links in new and edit mode. Select Yes to remove the ability to add or delete a new row to the repeating section in new and edit mode. Expressions may be used to allow a row to be added or deleted only in new mode, and not edit mode, or vice versa. | No |
Formatting | Item CSS class | The CSS item to apply to the item. | No |
| Alternate item CSS class | The CSS class to apply to every alternate item (row). | No |
| CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings). | No |
| Border | Draws a line along the selected border of the control. | No |
| Border Style | The style of the border. | No |
| Border Width (Pixels) | The width of the border in pixels. | No |
| Border Color | The color of the border. | No |
Getting started with the form designer
Control Settings
Controls In Use
Connecting Controls to fields or variables
Shortcut keys
Inserting reference fields
Control Properties Ribbon
The Recurrence control allows a user to make the calendar item a repeating event. A user can edit the reoccurrence pattern when filling in the form.
Note: The Recurrence control is only available when a form is designed from a Calendar list.
Note: The Recurrence control is not supported in Nintex Mobile.
Section | Selection | Description |
General | Visible | Hide or show the control at runtime. |
Formatting | CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings). |
| Border | Draws a line along the select border of the control. |
| Border Style | The style of the border. |
| Border Width (Pixels) | The width of the border in pixels. |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. |
Advanced | Resize at runtime | Allow the control to dynamically adjust its size and adjust the form size and position of other controls accordingly. |
The Calculated Value control performs a calculation or concatenation (depending on the data type of the values used within the Formula Builder) and displays the result at run time.
Section | Selection | Description | Nintex Mobile |
General | Formula | The runtime formula to be calculated. Use the Formula Builder to create the formula. |
Yes |
| Name | The name of the control. The name is used for comparison validation and other control references. | Yes |
| Connected to | The field to bind the input control to. | Yes |
| Save as data type | The data type to convert to when the form is saved. If Decimal is selected:
If Decimal or Integer is selected:
|
Yes |
| Value prefix | The prefix for the value. | Yes |
| Value suffix | The suffix for the value. | Yes |
| Recalculate formula on view mode | Recalculate the value when the form is displayed in view mode at run time. | No |
| Recalculate formula on new mode | Recalculate the value when the form is displayed in new mode at run time. By default, this is set to yes. | No |
| Recalculate formula on edit mode | Recalculate the value when the form is displayed in edit mode at run time. By default, this is set to yes. | No |
Appearance | Visible | Hide or show the control at run time. | Yes |
| Enabled | Enable the control to receive user input at run time. | Yes |
Formatting | Control CSS class | The CSS class to apply to the inner elements of the control. | No |
| CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings). | No |
| Border | Draws a line along the selected border of the control. | No |
| Border Style | The style of the border. | No |
| Border Width (Pixels) | The width of the border in pixels. | No |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. | No |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. | No |
Advanced | Help text | Text that will be displayed to the user as a tooltip to guide the completion of the form. | No |
| Control Mode | Force control to be in Edit mode, Display mode, or set to Auto. | No |
| Convert empty string to null | Convert to a null value if the control contains an empty string. | No |
| Null display text | If the bound value is null, this value will be displayed instead. | No |
| Store Client ID in JavaScript variable | A JavaScript Variable will be created that references the Client ID of this control. If Yes is selected:
|
No |
| Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form size and position of other controls accordingly. | No |
Getting started with the form designer
Control Settings
Controls In Use
Shortcut keys
Inserting reference fields
Formula Builder
Control Properties Ribbon
Managed metadata is a hierarchical collection of managed terms that must be defined within SharePoint prior to use in Nintex Forms. For more information on managed metadata refer to http://technet.microsoft.com/en-us/library/ee424402.aspx.
The Managed Metadata control retrieves these managed terms from your SharePoint environment. Once a data selection has been configured, users can select values from a list of set terms, allowing for more accurate selections.
Note: The Managed Metadata control is not supported in Nintex Mobile.
The External Data Column control enables users to add data from external content types to standard SharePoint lists. Just like an external list, the external data column can display data from any external content type. For more information on external data columns, refer to http://msdn.microsoft.com/en-us/library/ee558737.aspx.
Note: To use the external data column, the external content type must first be configured. For more information on setting up external content types, refer to http://msdn.microsoft.com/en-us/library/ff728816.aspx.
Note: The External Data Column control is not supported in Nintex Mobile.
Section | Selection | Description |
General | Name | The name of the control. The name is used for comparison validation and other control references. |
| Connected to | The field to bind the control to. |
| External content type | Use the external content type picker to choose a content type. |
| Display format | The format to display the control as (Default picker, Drop down list, Option buttons). Note: This will make a call to the external content type to read in all items in the external list. If you use a drop down list or option buttons, this could present a performance issue if there is a larger number of items. |
| Field to be displayed | The field name from the external content type to be displayed. |
| Additional fields | When the External Data Column control is bound to an external data column in the list or library, this field lists additional field-specific columns configured for the external data column. For example, if you bind the control to the external data column “Customer,” which is configured using the CustomerCRM external type to show the fields CustomerName and PhoneNumber, then these fields are listed here. For more information about external data column configuration, see the following Microsoft article: “Create and update an external data column in a list or library.” |
Appearance | Visible | Hide or show the control at runtime. |
| Enabled | Enable the control to receive user input during runtime. |
| Dialog title | The text to display in the dialog box. |
Formatting | Control CSS class | The CSS class to apply to the inner elements of the control. |
| CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings). |
| Border | Draws a line along the selected border of the control. |
| Border Style | The style of the border. |
| Border Width (Pixels) | The width of the border in pixels. |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. |
Validation | Required | The form will not submit unless this control is completed correctly. |
| Use custom validation | Enables the custom JavaScript validation for the control. |
Advanced | Help text | Text that will be displayed to the user as a tooltip to guide the completion of the form. |
| Control Mode | Force control to be in Edit mode, Display mode, or set to Auto. |
| Store Client ID in JavaScript variable | A JavaScript variable will be created that references the Client ID of this control. If Yes is selected:
|
| Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form size and position of other controls accordingly. |
The Control Properties Ribbon varies between each control. Please refer to the list below for more information about each property.
Manage form controls
Form and Layout settings
Control Settings
The Geolocation control enables users to specify location by either pressing a button to locate their current longitude and latitude or by manually entering coordinates.
Note: To use the "Use my location" functionality the client's browser needs to support the appropriate functionality and the use of the form needs to permit the form to use it. If the user's browser or the SharePoint site's master page has disabled HTML5 capabilities then the user will need to specify the location manually.
Note: For an extensive list of the control properties Ribbon, including descriptions, refer to the Control Properties Ribbon.
Getting started with the form designer
Control Settings
Controls In Use
Shortcut keys
Inserting reference fields
Control Properties Ribbon
Section | Selection | Description |
General | Name | The name of the control. The name is used for control references to other controls. |
Appearance | Visible | Hide or show the control at runtime. |
Formatting | CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings |
| Border | Draws a line along the select border of the control. |
| Border Style | The style of the border. |
| Border Width (Pixels) | The width of the border in pixels. |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. |
Advanced | Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form size and position of other controls accordingly. |
Selection | Setting |
Request Method | POST |
Request Header | |
Request Body | <soapenv:Envelope xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/'> <soapenv:Body> <GetListCollection xmlns='http://schemas.microsoft.com/sharepoint/soap/'></GetListCollection> </soapenv:Body> </soapenv:Envelope> |
Content Type | text/xml; charset="utf-8" |
Section | Selection | Description |
General | Name | The name of the control. This name is used for comparison validation and other control settings. |
| ID connected to | The column to which to bind the XPath for value field. Note: The selected column must be within the current list and must be of the type “Single line of text.” Note: When Label or Text is selected for Display format, this field can only bind to XPath for display; XPath for value cannot be bound. |
| Text connected to | The column to which to bind the XPath for display field. Note: The selected column must be within the current list and must be of the type “Single line of text.” |
Display format | The type of control to display. Select one of the following options.
Default value: Drop down list | |
| Service URL | Path to REST or SOAP service. Example: http://sales.crestan.com:8084/ProductService.svc/web/products Note: You can insert references to named controls. For example, the form might have a named control for specifying the service URL to use for the call. Inserted references are formatted as red underlined font. |
Request method | Select an option.
| |
| Timeout (seconds) | Period of time to attempt sending the request. Note: The request is not executed if the value is 0. Default value: 10. |
| Request body | (This field is displayed when POST is selected for Request method.) |
| Content type | Specify the body type. Example: text/xml; charset="utf-8" (This field is displayed when POST is selected for Request method.) |
| Authentication type | Select an option.
|
| Secure Store target application ID | Enter the target application ID stored in SharePoint Secure Store Service containing credentials for the service. The Secure Store Service must be in the default application proxy group. To view the proxy group for the service, use the Service Application Associations page in Central Administration. For more information about Secure Store Service on SharePoint, see the Microsoft article Configure the Secure Store Service in SharePoint 2013. (This field is displayed when the value selected for Authentication Type is something other than Anonymous.) |
| XPath for value | Value element for the XPath expression of the request. Example: //ID For information about XPath syntax, see http://www.w3schools.com/xpath/xpath_syntax.asp. (This field is displayed when Drop down list is selected for Display format.) Note: Items lacking value or display are ignored. |
| XPath for display | Display element for the XPath expression of the request. Example 1: //Name Example 2: //*[name() ='List']/@Title For information about XPath syntax, see http://www.w3schools.com/xpath/xpath_syntax.asp. (This field is displayed when Drop down list is selected for Display format.) Note: Items lacking value or display are ignored. |
| Execute in new mode | Default: Yes. |
| Execute in edit mode | Default: Yes. |
| Execute in view mode | Default: No. |
Appearance | Visible | Hide or show the control at runtime. |
| Enabled | Enable the control to receive user input at runtime. |
| Use custom "Please select" text | Specify whether or not to use custom "Please select" text. (This field is displayed when Drop down list is selected for Display format.) |
Filtering | Filter available selections | Select one of the following options.
|
| XPath for Where field | XPath expression for the field in the source list to apply the filter to. For example, you might specify an XPath expression for a field that lists product names: //ProductName |
| Filtered by value | The value to filter selections by. Note: You can insert references to named controls. Inserted references are formatted as red underlined font. For example, you might insert a reference to a named control on the form that is used to specify the location. |
Formatting | Control CSS class | The CSS class to apply to the inner input control. |
| CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings). |
| Border | Draws a line along the select border of the control. |
| Border Style | The style of the border. |
| Border Width (Pixels) | The width of the border in pixels. |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. |
Validation | Required | The form will not submit unless this control is completed correctly. |
| Required error message | Text to display if the control is not completed correctly. (This field is displayed when Yes is selected for Required.) |
| Use custom validation | Enables custom JavaScript validation for the control. |
| Custom validation function | Specify the JavaScript function name for the client side custom validation. Note: The JavaScript function is to be specified in the Custom JavaScript section within the form's Settings. (This field is displayed when Yes is selected for Use custom validation.) |
| Custom error message | The error message to display when an invalid value is entered. (This field is displayed when Yes is selected for Use custom validation.) |
Advanced | Custom headers | (Optional.) Headers for the request, as name/value pairs. For examples of header values, see "Supported headers" below. Click Add to specify a header. Note: When specifying values, you can insert references to named controls. |
| Help text | Help text that will be displayed to the user as a tooltip to guide the completion of the form. |
| Control Mode | Force control to be in Edit mode, Display mode, or set to Auto. |
| Confirm value in connected column | When enabled, displays a warning on form submission if bound column values were updated outside Nintex Forms. Note: Columns are bound to the control via the fields ID connected to and Text connected to. An example scenario for display of this warning is updating the value of the "Department" column for the related list item using SharePoint and then attempting to submit the form for that list item where the form control is bound to the "Department" column. |
| Store Client ID in JavaScript variable | A JavaScript Variable will be created that references the Client ID of this control. |
| Client ID JavaScript variable name | The name of the variable to store the Client ID in. (This field is displayed when Yes is selected for Store Client ID in JavaScript variable.) |
| Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form length and position of other controls accordingly. |
This section lists supported and unsupported headers for use in the Custom headers field. Examples are provided for supported headers.
Examples of supported headers
Accept-Charset: utf-8Ignored headers (see parenthetical comments)
Getting started with the form designer
Control Settings
Controls In Use
Connecting Controls to fields or variables
Shortcut keys
Inserting reference fields
Control Properties Ribbon
The SQL Request control allows you to look up values from SQL databases. Use this control to populate drop-down lists and other display formats in your forms. Retrieve data from SQL databases by specifying server, database, authentication, stored procedure, and optionally stored procedure parameters for dynamic filtering. Using the values retrieved from the SQL database, the SQL Request control selects the value and display fields. The value field is stored in the specified column (see the control field “Value field”) while the display field is displayed on the form (see the control field “Display field”).
Note: The SQL Request control is not supported in Nintex Mobile.
SQL credentials are retrieved from the SharePoint Secure Store service. You can test configuration using the Run Now dialog box.
Example scenarios:
The ribbon for the SQL Request control displays the following buttons.
Run Now: Displays the Run Now dialog box. For more information, see Run Now.
Note: For an extensive list of the control properties ribbon, including descriptions, see Control Properties Ribbon.
Section | Selection | Description |
General | Name | The name of the control. This name is used for comparison validation and other control settings. |
| ID connected to | The column to which to bind the value field of the returned value. Note: The selected column must be within the current list and must be of the type “Single line of text.” Note: When Label or Text is selected for Display format, this field can only bind to the display field (Display field); Value field cannot be bound. |
| Text connected to | The column to which to bind the display field of the returned value. Note: The selected column must be within the current list and must be of the type “Single line of text.” |
| Display format | The type of control to display. Select one of the following options.
Default value: Drop down list |
| Server | Server hosting the SQL database. |
| Database | The SQL database. |
| Connection timeout (seconds) | Period of time to attempt sending the request. Note: Do not specify 0 as this value indicates no limit and causes indefinite waits for connection attempts.
Default value: 10. |
| Authentication type | Select one of the following options.
|
| Secure Store target application ID | Enter the target application ID stored in SharePoint Secure Store Service containing credentials for the service. The Secure Store Service must be in the default application proxy group. To view the proxy group for the service, use the Service Application Associations page in Central Administration. For more information about Secure Store Service on SharePoint, see the Microsoft article Configure the Secure Store Service in SharePoint 2013. |
| Query type | Select one of the following options.
Default value: Stored procedure. Note: To prevent SQL injection, Nintex recommends using stored procedures instead of free-form SQL queries. As a further security measure, Nintex recommends leveraging a read-only connection to the database. For more information about preventing SQL injection, see the Open Web Application Security Project (OWASP) article SQL Injection Prevention Cheat Sheet. |
| Stored procedure name | Specify the name of the stored procedure. (This field is displayed when Stored Procedure is selected for Query type.) |
| Stored procedure parameters | When parameter name/value pairs are specified, filters the results from the stored procedure. You can filter using values of other controls on the form. For example, let's say that the form includes named controls "Category" and "Year." You want the form to display product names (Display field) from the stored procedure results (Stored procedure name), but dynamically filtered for the entered category and year. In this scenario, you add a parameter referencing the named control "Category" and another parameter referencing the named control "Year." At runtime, the displayed product names correspond to values entered for these named controls. Click Add to specify a parameter. (This field is displayed when Stored Procedure is selected for Query type.) |
Query | Type a free-form SQL query. (This field is displayed when SQL is selected for Query Type.) Note: To prevent SQL injection, Nintex recommends using stored procedures instead of free-form SQL queries. For more information about preventing SQL injection, see the Open Web Application Security Project (OWASP) article SQL Injection Prevention Cheat Sheet. Note: You can insert references to named controls. Inserted references are formatted as red underlined font. The following example query selects employee IDs and first names based on the value specified for the named control "Title." The employee ID is used as the value field and the name is used as the display field. select FirstName, EmployeeID from Employees where Title like 'Title' | |
| Value field | Column for retaining value of selected item. |
| Display field | Result column to display on the form. |
| Execute in new mode | Default: Yes. |
| Execute in edit mode | Default: Yes. |
| Execute in view mode | Default: No. |
Appearance | Visible | Hide or show the control at runtime. |
| Enabled | Enable the control to receive user input at runtime. |
| Use custom "Please select" text | Specify whether or not to use custom "Please select" text. |
Formatting | Control CSS class | The CSS class to apply to the inner input control. |
| CSS class | The CSS class to apply to the control. This is used to apply advanced styling options. The Custom CSS class is defined in Form Settings (refer to Form and Layout settings). |
| Border | Draws a line along the select border of the control. |
| Border Style | The style of the border. |
| Border Width (Pixels) | The width of the border in pixels. |
| Border Color | The color of the border. This can either be a HEX code or a named color that is supported by html. |
| Padding Width (Pixels) | The amount of padding in pixels that will appear between the top, left and right border and the inner control. |
Validation | Required | The form will not submit unless this control is completed correctly. |
| Required error message | Text to display if the control is not completed correctly. (This field is displayed when Yes is selected for Required.) |
| Use custom validation | Enables custom JavaScript validation for the control. |
| Custom validation function | Specify the JavaScript function name for the client side custom validation. Note: The JavaScript function is to be specified in the Custom JavaScript section within the form's Settings. (This field is displayed when Yes is selected for Use custom validation.) |
| Custom error message | The error message to display when an invalid value is entered. (This field is displayed when Yes is selected for Use custom validation.) |
Advanced | Help text | Help text that will be displayed to the user as a tooltip to guide the completion of the form. |
| Control Mode | Force control to be in Edit mode, Display mode, or set to Auto. |
| Confirm value in connected column | When enabled, displays a warning on form submission if bound column values were updated outside Nintex Forms. Note: Columns are bound to the control via the fields ID connected to and Text connected to. An example scenario for display of this warning is updating the value of the "Department" column for the related list item using SharePoint and then attempting to submit the form for that list item where the form control is bound to the "Department" column. |
| Store Client ID in JavaScript variable | A JavaScript Variable will be created that references the Client ID of this control. |
| Client ID JavaScript variable name | The name of the variable to store the Client ID in. (This field is displayed when Yes is selected for Store Client ID in JavaScript variable.) |
| Resize at runtime | Allow the control to dynamically adjust its size, and adjust the form length and position of other controls accordingly. |
Section | Selection | Description |
General | Name | The name of the control. The name is used for comparison validation and other control references. |
Note:
Select any control on the canvas by left-clicking with the mouse on it.
To select multiple controls:
Note: Changes to Rules cannot be undone; with the exception of deleting a rule.
1. Select the List tab on the List Tools Ribbon.
2. In the Customize List group, click the Nintex Forms button to edit the default list form. If the list contains multiple content types, click the drop- down and select Customize the [Content Type] Form from the menu options.
To create a new form in Nintex Workflow (requires Nintex Workflow to be installed and configured), refer to Designing forms in Nintex Workflow for more information.
The Nintex Forms designer will open in the current window.
1. Navigate to the content type's information page (e.g. Site Actions > Site Settings > Site Content Types).
2. In the Settings section, click on Edit form with Nintex Forms.
The Nintex Forms designer will open in the current window.
Note: All lists using the content type will inherit the designed Nintex form.
Controls In Use
Control Settings
Print to PDF
Form and Layout settings
Saving and publishing forms
Importing and exporting forms
Live Forms settings
Manage device layouts
Designing forms in Nintex Workflow
Rules
Form Variables
A shortcut key is a combination of keys that executes a specific function or command within the Nintex Forms application.
The following are the shortcut keys that are available for use when designing a form in Nintex Forms:
Shortcut keys | Description |
---|---|
Ctrl + Shift + A | Select all controls on the layout |
Ctrl + Shift + C | Copy the selected control(s) to the clipboard |
Ctrl + Shift + X | Remove the selected control(s) and copy to the clipboard |
Ctrl + Shift + V | Paste the copy/cut control(s) from the clipboard |
Ctrl + Shift + B | Bring the selected control(s) to the front |
Ctrl + Shift + S | Send the selected control(s) to the back |
Ctrl + Z | Undo last action |
Ctrl + Y | Redo most recent undo |
Delete | Delete the selected control(s) |
Ctrl + Shift + F | Copy the font and styles from the selected control(s) using Format Painter. |
Getting started with the form designer
Linked Controls
Control Settings
Controls In Use
Nintex forms can be imported and exported to the local file system as '.xml' files. This is useful when copying forms from one server to another or for other file transfer scenarios.
The exported file can then be imported into a different SharePoint List, workflow action or another workflow, or as a template. When exporting a form, all of the configured device layouts are included in the export file. This results in all device layouts being imported when importing the file as a form or as a template. Please refer to Associating templates to device layouts for more information.
To export the form:
Note: When importing a form it will overwrite any of the current form design.
Note: When exporting a Nintex Workflow that includes forms edited in Nintex Forms, the forms will be included in the Nintex Workflow export file(.nwf).
Associating templates to device layouts
Form and Layout settings
Saving and publishing forms
The Controls In Use pane can be used to easily identify which controls are:
Use the Connected to property when specifying the field (list column) or workflow variable that the control will read and store data to. (This is also known as "binding” the control to the field or variable).
Note: If the form has been saved and changes are made to a field (list column) or workflow variable that is Connected to a control, the control on the form will not be updated. Either manually make the changes to the control settings, or remove the control from the form and re-add the pre-configured control onto the form using the Controls Toolbox. An example would be the choices available for selection in a Choice control. The Choice control on the form will retain the same values as when the form was saved.
Note: If a default value is specified for the field or workflow variable that the control is being Connected to, this value will overwrite any default value specified for the control.
Getting started with the form designer
Control Settings
Inserting reference fields
Linked Controls
Layouts allow a form to be targeted to different mobile devices using defined screen dimensions set in the Manage device layouts settings. Additionally, some layouts are especially designated for the Nintex Mobile App.
The first time a device layout is selected for a form, the controls currently on the default layout will be copied to the selected device layout.
Add or remove controls as required and adjust the position, size, and settings of the controls to suit the device layout.
Note: The Controls In Use panel may be helpful in identifying controls that are in use on other layouts which are not on the current layout.
Creating a form layout for the Nintex Mobile App is the same as creating a layout for viewing through the browser.
However, please note:
Getting started with the form designer
Importing and exporting forms
Manage device layouts
Controls In Use
Saving and publishing forms
Forms functionality supported for use with Nintex Mobile
Insert references to create dynamic values to be used in settings or displayed as text. Reference tokens and functions are calculated at runtime and the resulting values are used in the form.
To insert a reference:
Reference categories are indicated by tabs in the Insert Reference dialog box. Availability of reference categories depends on the context in which the Insert Reference dialog box is accessed. Following are possible reference categories.
Note: Additional references are available when designing a form in Nintex Workflow. Please refer to the Nintex Workflow help file for more information.
Related Topics
Getting started with the form designer
Inline functions
Inline functions usage examples
In any text input that supports inserting reference fields, an inline function can be entered which will be resolved to a value at runtime.
A number of functions are provided out of the box.
Functions can also be used as arguments for other functions.
The parsing engine replaces any inserted reference tokens first, and then the resulting text is evaluated for functions.
If a function contains another function as an argument, the inner most function will be evaluated first.
As reference tokens are replaced first, the reference token can also contain function syntax that will be evaluated.
Functions cannot refer to named controls.
Returns the value for a specific key in the query string. This can be used to specify default values for the People and Single Line Textbox controls by including query string parameters in the URLs that opens the form in New mode.
If the key cannot be located in the query string, a blank value will be returned. If there is any potentially damaging JavaScript in the value, it will be removed before being inserted into the form or control settings.
Usage
fn-GetQueryString(key)
Arguments
key: a string that represents the parameter name passed to the form via the query string.
Returns true if the second argument is greater than the first argument.
Usage
fn-GreaterThan(value1, value2)
Arguments
Returns true if the second argument is greater than or equal to the first argument.
Usage
fn-GreaterThanOrEqual(value1, value2)
Arguments
Returns true if the second argument is less than the first argument.
Usage
fn-LessThan(value1, value2)
Arguments
Returns true if the second argument is less than or equal to the first argument.
Usage
fn-LessThanOrEqual(value1, value2)
Arguments
Bool value: A value that evaluates to either true or false.
Returns true if the first argument starts with the second argument.
Usage
fn-StartsWith(value1, value2)
Arguments
fn-SubString(sourceString, startIndex, length)
When a control is on the form, there are three ways to open the control settings:
Note: If a control has mandatory settings, a message will appear to show which settings require configuration.
Note: In addition to the tooltip warning message, a yellow warning bar will appear at the top of the design canvas. This will alert the form designer that one or more controls on the form contain incomplete configurations. It will not be possible to publish the form or the associated Nintex Workflow if any of the form's controls have incomplete configurations.
Getting started with the form designer
Connecting Controls to fields or variables
Controls In Use
List of controls
A form must be published in order to make it available to users. Published forms are automatically saved. Use the Save button to save changes to the form design without publishing.
In addition to the standard SharePoint publishing, forms can also be published to Nintex Live, an internet hosted service. For information on publishing to Nintex Live, refer to Publishing forms to Nintex Live below.
To save a form:
The Confirm save dialog displays
- The device specific layouts that will be published with the form.
- The Live Settings configuration for the form (if Nintex Live Forms has been enabled). The Live Settings configurations can be changed by clicking on the Change link.
- Any mobile details as far as Nintex Mobile layouts created.
- The option to skip 'Confirm save" and "Save completed" dialogs. Selecting this option will no longer show the dialogs for the current form, on the current browser, until the option is rest in the "Form Settings" dialog. When selected, a toaster notification will be shown informing the user when the form has been saved successfully.
A Form saved successfully message will be displayed just below the Ribbon at the top right of the design canvas.
Note: If designing and editing a form in Nintex Workflow using Nintex Forms, only the Save button is available in the form designer Ribbon. The form is published when the workflow is published. Refer to Designing forms in Nintex Workflow for more information.
Before a form becomes available to users within SharePoint lists and libraries, it must be published.
Note: If there are any form or control settings that have not been configured, the Publish button will be disabled.
To publish a form:
- The device specific layouts that will be published with the form.
- The Live Settings configuration for the form (if Nintex Live Forms has been enabled).
- The Live Settings configurations can be changed by clicking on the Change link.
3. Click Publish.
This may take a few seconds. A Form published successfully message will display.
If the Publish and Close option is selected the form will close immediately after a successful publish.
Note: The form is automatically saved before it is published. It is not necessary to Save and then Publish a form.
Note: If a published form has controls that are connected to columns, workflow variables or labels that are associated to a bound control; property changes made to the columns or workflow variables will be automatically synchronized to the Nintex form without needing to republish the form.
In addition to the standard SharePoint publishing, forms can also be published to Nintex Live to provide access via the internet.
Note: Only the following form types can be published to Nintex Live:
To configure settings for Nintex Live publishing:
To publish a form to Nintex Live:
If a published form has controls that are connected to columns, workflow variables or labels that are associated to a bound control; property changes made to the columns or workflow variables will be automatically synchronized to the Nintex form without needing to republish the form. However, if the form has already been published to Nintex Live, it must be republished to Nintex Live for the changes to reflect on the Live form.
If a workflow is configured to start when a new item is created:
The following are controls that cannot be rendered by Nintex Live. These controls will not appear in the form when viewed via Nintex Live:
Note: Task delegation scenarios are not supported in Nintex Live. If a workflow task form has a delegation link, it will be hidden.
Live Settings
Getting started with the form designer
Designing forms in Nintex Workflow
Form and Layout settings
The Settings dialog includes settings that apply to the current layout, and advanced settings that apply to the form in general.
Selection | Field | Description |
General | Grid cell height (pixels) | The height of the grid cells on the current layout. |
| Grid cell width (pixels) | The width of the grid cells on the current layout. |
| Canvas height (pixels) | The height of the current layout. |
| Canvas weight (pixels) | The width of the current layout. |
| Snap to grid | When this setting is set to Yes, all controls on the layout are automatically positioned to the nearest gridline. |
| Show grid lines | When this setting is set to Yes, the grid lines on the designer canvas will be displayed. |
| Skip "Confirm publishing/save" and "Publish completed" dialogs | When this is checked, the publish list forms and the save in workflow forms will not show dialogs, and will be replaced with notification messages. |
Appearance | Layout CSS class | The CSS classes to apply to the layout at runtime. The styles for a CSS class can be defined in the Custom CSS section. |
| Font family | The default font for all controls on the layout. |
| Font size (pt) | The default font size for all controls on the layout. |
| Background color | The background color for the layout. |
| Font color | The default text color for all controls on the layout. |
| Horizontal alignment | The default text alignment for all controls on the layout. |
| Background image URL | The URL of an image to use as the background of the layout. |
| Background image repeat | Specify if the background image will repeat. |
| Form CSS class | The CSS classes to apply to all layouts for the form at runtime. The styles for a CSS class can be defined in the Custom CSS section. |
Advanced | Redirect URL | The URL to redirect to after the form has been submitted successfully. |
| Target user agents | The user agents used to determine when this layout is used at runtime. Enter each user agent on a new line. |
| Custom CSS includes | The URLs to the custom CSS files to include at runtime. Enter each URL to the custom CSS on a new line. |
| Custom JavaScript Includes | The URLs to the custom JavaScript files to include at runtime. Enter each URL to the custom JavaScript on a new line. |
Custom CSS | | Custom CSS styles to be included with the form at runtime. All custom CSS styles defined, can be used for a single layout (Layout CSS class), all layouts (Form CSS class) and individual controls (Control CSS class). By default, the Nintex Forms CSS styles used by all forms are provided. For more information on CSS classes used in Nintex Forms, please refer to CSS Styles. |
Custom JavaScript | | Custom JavaScript to be included with the form to process runtime logic. |
List Form Webpart | Configure List Form Webpart Confirmation Message | When set to Yes, this will allow you to specify a message to be displayed inside the list form web part once it is successfully submitted. This is an alternative to the redirect or the basic success message that displays above the web part. |
Nintex Mobile Settings | Use Default Form Name and Form Description | Check this box to use the default form name and form description. Uncheck the box to change these titles. This will override the title and description of the form when displayed on your Nintex Mobile App. |
| Category | Assign a category for the form to be displayed in. This is recommended. Forms without an assigned category will be displayed in the Nintex Mobile App under the "no category" group. |
| Icon | The full URL of the icon that is displayed in the Nintex Mobile App for this specific form. |
| Use SharePoint Server Timezone | When unchecked and a user accesses the form, their local time will be displayed. Check the box to use the timezone of the SharePoint server. |
Print to PDF | Page Size | The size options. Select one of the following.
Default value: A4 |
| Page Orientation |
The orientation options. Select one of the following.
Default value: Portrait |
Getting started with the form designer
Importing and exporting forms
Saving and publishing forms
Control Settings
Inserting reference fields
Page Break Guide
Print to PDF
In addition to the standard SharePoint publishing, forms can be published to Nintex Live. Use the Live Settings option to configure settings for Nintex Live publishing.
Note: The Live Settings option is only enabled when Nintex Live Forms is enabled in Central Administration and the feature is activated on the site collection.
The message to be displayed to the user when a form submission is cancelled.
The message to be displayed to the user after the form is submitted successfully.
Refer to Saving and publishing forms for more information.
Live Forms settings
Installing Nintex Live
Activating Nintex Forms
View Live forms
Saving and publishing forms
A Linked Control is a control that exists on more than one device layout. Any changes (formatting, settings) made to the control on one layout will affect all layouts containing that control.
OR
Linked Controls cannot be unlinked directly. To achieve the desired effect, create a second copy of the control on the same layout, and then delete the Linked Control.
Controls In Use
Getting started with the form designer
Control Settings
Form and Layout settings
Nintex Forms can be used to edit and design workflow start forms and task forms from within Nintex Workflow.
Note: To design forms using Nintex Forms in Nintex Workflow, the Nintex Forms for Nintex Workflow site collection feature must be activated. Refer to Activating Nintex Forms for more information.
The following Nintex Workflow forms can be edited using Nintex Forms:
Note: Nintex Forms does not support editing and designing Nintex Workflow forms in User Defined Actions.
To design or edit Nintex Workflow forms using Nintex Forms:
When designing start forms - The start form is auto-generated. All workflow variables that are set to Show on start form are added to the form when the form is first edited in Nintex Forms. Once the form has been saved, any new workflow variables that are set to Show on start form will not be displayed on the form. To add the new workflow variable onto the form, drag and drop the control from the Workflow Variable group in the Form Controls toolbox onto the form canvas.
When designing task forms for Assign Flexi task - The task form is auto-generated. The Outcomes are automatically added to the Decision choice control when the form is first edited in Nintex Forms. Once the form has been saved, any changes to the Outcomes will not be reflected in the Decision choice control. The values in the Decision choice control must be updated manually.
When a workflow action containing a form created with Nintex Forms is copied and pasted, each action will share the form by default.
When the form is edited, a dialog message will confirm whether a separate instance of the form should be created.
Note: Once a separate instance of the form has been created and saved, the action cannot will not be able to revert back to the original shared form.
Task forms (list and site workflow), and start forms (site workflow only), created with Nintex Forms can be published to Nintex Live.
To provide assignees with the URL to access the Nintex Live Form:
When a site workflow start form is submitted by an anonymous user, the workflow will run under the identity of the form designer.
When a site workflow start form is submitted by an authenticated user, the workflow will try to run using the authenticated user's credentials if the user can be found in Active Directory. If the user credentials cannot be found, the workflow will run under the identity of the form designer. If the user is found but has no access to the site, the workflow will run under the identity of the form designer.
Activating Nintex Forms
Getting started with the form designer
Live Settings
Saving and publishing forms
Inserting reference fields
CSS stands for Cascading Style Sheets. Styles can be used to define how elements (including controls) on a form are displayed. Refer to w3schools.com for more information on CSS.
Note: Customizing the CSS styles is an advanced feature and should be approached with caution.
The following are the CSS styles that can be defined in the Custom CSS section within the Form and Layout settings when designing a form in Nintex Forms:
CSS class |
Description |
---|---|
.nf-form-input |
The upper most level DIV of controls that can accept a value. |
.nf-filler-control-inner |
The DIV that is below the upper most level DIV on any control. |
.nf-form-label |
The upper most level DIV of each label control on a layout. |
.nf-textbox-wrapper |
The parent element of the Single Line Textbox control. |
.nf-section |
The upper most DIV of any control. |
.nf-section-bottom |
The line below the last input control on a layout. |
.nf-mobile-form |
The outer DIV of mobile device layouts. |
.nf-item |
The odd numbered rows in the repeater control. |
.nf-item-alternating |
The even numbered rows in the repeater control. |
.nf-non-dialog-outer |
The outer DIV of the entire layout when it is loaded into a new tab/window instead of a SharePoint modal dialog. |
.nf-filler-wrapper-outer |
The first child DIV of the outer-most DIV. |
.nf-filler-wrapper |
The first child DIV of .nf-filler-wrapper-outer. |
.nf-repeater-row |
All the rows in the repeater control. |
.nf-container-inner |
The first child DIV of the parent DIV generated around a control. |
.nf-image |
The image control. |
.nf-label-control |
The label control. |
.nf-form-footer |
The footer information used by list forms and task forms. |
.nf-form-line |
The inside of the footer that draws a line to show the end of the form. |
.nf-validation-summary |
The DIV used to display any validation errors on the form. |
.nf-error-highlight |
The DIV used to highlight a control that contains validation errors. |
Form and Layout settings
Getting started with the form designer
Control Settings
Formula Builder can be used to create calculated and concatenated values which can be displayed using a calculated value control which will display at run time. The Formula Builder is different from inline functions as the inline functions are resolved on form load at run time.
Depending on the composition of the formula, the value that is displayed in the calculated value control will always calculate to reflect the current values entered in named controls that are included in the formula.
The formula builder supports Named Controls. A Named Control is when a control that has been added to the form is given a name. Most controls can be named by setting the Name property within the General section of the control.
If the data type of all the values in the formula is a number, the formula will calculate the value.
String concatenations can be created by including the "+" symbol between named controls and string or number values.
The runtime functions can be used to perform calculations for a set of values.
Examples of use:
Calculated Value
Inserting reference fields
Control Settings
Runtime Functions
The following are examples on how to toggle the appearance (visible or enabled) of a control using an expression:
Inserting reference fields
Inline functions
Rules can be used to add dynamic formatting, visibility or editability changes to controls within any form based on defined conditions.
To open the Rules pane, select the Rules button on the Nintex Forms Design Ribbon. Alternatively, select Add Rule in the Control Properties Ribbon.
By default, the Rules pane will show only those rules which are associated with every control currently selected. To show all rules included in the form, check the "Show all rules" box.
Note: Once Add new rule is selected, the rule is automatically created. To delete a rule, click on the drop-down menu beside the rule and select Delete rule.
The name of the selected rule. The name can be changed in the Name field on the Rules pane.
The type of the selected rule. Select from either formatting or validation.
Validation
The condition that will mark the control as invalid and prevent the form from being submitted if the condition expression evaluates to TRUE. If the expression evaluates to FALSE, the rule will not be triggered. The formula builder button (to the right of the Condition field) can be used to aid construction of condition formulas.
The form will not be submitted if the validation rule evaluates to TRUE.
The rule should be applied to the control for which you want to highlight the issue. If the rule does not evaluate, a red box will appear around the relevant control. If multiple fields need to be marked as invalid, the rule can be applied to multiple controls.
Message
The message to be displayed when the validation rule is triggered.
Conditional validation rule example:
A form has two input controls, a single line of text which is called "Amount" and a multi-line text control called "Clarification". To the "Clarification" control a validation rule is added with the condition "Amount>1000&&isNullOrEmpty(Clarification)". If a user enters an amount greater than 1000 in the form, they cannot submit the form unless they have explained the expense in the "Clarification" control.
Note: Design or Full Control permissions are required to apply HTML formatting in validation rule messages. Insufficient permissions result in encoded HTML formatting. For example, the validation rule message "<b>Select quantity</b>" is formatted to appear as "Select quantity" in forms published with sufficient permissions; however, in forms published with insufficient permissions, the message appears with the encoded HTML tags ("%/ltSelect quantity%/gt").
The condition that will trigger the rule is set in the Condition field. The formula here must resolve to the value of TRUE for the instruction on the rule to be triggered, any other value will be treated as a FALSE value and the rule will not be triggered. The formula builder button (to the right of the Condition field) can be used to aid construction of condition formulas.
Syntax for conditions can include any variables available in the formula builder; including Item Properties and Named Controls. Runtime functions and standard mathematical symbols can be used to manipulate or compare values for the purpose of crafting a condition. In addition, the following symbols can be used as comparison operators. String literals must be contained in double quotes (e.g. Option=="High").
Symbol | Meaning |
---|---|
== | is equal to |
=== | is exactly equal to (value and type) |
!= | is not equal |
!== | is not equal (neither value or type) |
> | is greater than |
< | is less than |
>= | is greater than or equal to |
<= | is less than or equal to |
&& | and |
| | | or |
! | not |
Use the {Self} variable (available in the Named Controls tab in the Formula Builder) to reference the value in control associated to a rule within a condition. For instance, set a rule's condition to "{Self} > 5" if you want formatting to be applied to the control when it contains a value greater that 5.
Use Rules to modify the following formatting attributes of a control:
In addition, rules can be used to disable or hide controls. Note: When a control is hidden based on a rule, any associated labels will also be hidden.
To re-order the rules in the rules pane, drag and drop a rule into the desired position. Alternatively, click the drag texture on the rule you want to move and then click to where it is destined to be moved to.
Note: Rules are executed in the order they appear in the Rules pane. If a control has more than one rule applied to it, the rules will execute in the order set in the rules pane.
Click on the drop-down menu next to each rule to access additional functions.
Additional Functions | Description |
---|---|
Select associated controls | Selection of controls (and the Controls in Use pane) will be reset to all those controls on the current device layout associated with the current rule. |
Add to selected controls | Add the current rule to all of the selected controls. |
Remove from selected controls | Remove the current rule from all selected controls. |
Send to top | Rule will be moved to the top of the list of rules. |
Send to bottom | Rule will be moved to the bottom of the list of rules. |
Delete rule | Rule will be deleted from the form. |
A control within a repeating section may be associated with rules. These rules may include conditions which refer to controls in the same repeating section or controls outside of the repeating section.
However, controls outside the repeating section cannot include conditions which refer to controls within repeating sections; these conditions will always evaluate to FALSE.
The "checked controls" icon will appear beside the rule title in "Show all rules" mode to indicate this rule is associated with all the controls currently selected.
An "attention" icon will appear in the formatting section of the Rules pane to indicate that some currently unselected controls are associated with this rule. This serves as a reminder that some unselected controls will be affected by any changes to this rule.
To preview a form, select the Preview button on the Nintex Forms Design Ribbon.
The preview settings dialog will appear before the preview is displayed.
Notes: While viewing a preview, notifications may appear at the top of the preview itself. To close these, select "Close" in the bottom right-hand corner.
Forms designed for the Nintex Mobile App are not available for preview directly within the Nintex Forms Designer as it cannot render an accurate preview. When a mobile layout is specified as the device layout to preview, the platform and mode are not longer relevant. Once the Generate Preview button is clicked the form will be made available on Nintex Mobile only for the user who has designed the form. The form will be moved from the forms list once it has been submitted. An existing preview form will be overwritten if a new preview is generated.
If data is entered in a preview form (whether in the Designer or in the Nintex Mobile App), this data will not be saved.
Returns TRUE where both logical arguments are true. If either are false, returns FALSE.
Usage
and(boolean1, boolean2)
Returns the average value of a set of values.
Usage
avg([set of values])
Returns TRUE where string contains the element.
Usage
contains(string,element)
Returns the number of rows in which a control that has a value (not blank) appears within a repeating section.
Usage
count(control)
Returns the formatted currency string for the specified value.
Usage
currency(value)
Returns the row number of the Repeating Section the control is contained within.
Usage
currentRowNumber(Control)
Returns a new date contructed from the specified parameters.
Usage
date(day, month, yeah, hours, minutes)
Retuns the date with the specified number of whole days added to it.
Usage
dateAddDays(date, daysToAdd)
Element | Description | Example (in US date format) |
---|---|---|
"dd" | Day of month | 6/15/2009 1:45:30 PM -> 15 |
"ddd" | Day of week (Single Letter) | 6/15/2009 1:45:30 PM -> M |
"dddd" | Day of week (Full) | 6/15/2009 1:45:30 PM -> Monday |
"MM" | Month (Numeric) | 6/15/2009 1:45:30 PM -> 6 |
"MMM" | Month (Short) | 6/15/2009 1:45:30 PM -> Jun |
"MMMM" | Month (Full) | 6/15/2009 1:45:30 PM -> June |
"yyyy" | Year | 6/15/2009 1:45:30 PM -> 2009 |
"hh" | Hours (12 Hour) | 6/15/2009 1:45:30 PM -> 1 |
"HH" | Hours (24 hour) | 6/15/2009 1:45:30 PM -> 13 |
"mm" | Minutes | 6/15/2009 1:45:30 PM -> 45 |
"tt" | AM or PM | 6/15/2009 1:45:30 PM -> PM |
Format Specifier | Description | Example (in US date format) |
---|---|---|
"d" | Short date pattern | 6/15/2009 1:45:30 PM -> 6/15/2009 |
"D" | Long date pattern | 6/15/2009 1:45:30 PM -> Monday, June 15, 2009 |
"M", "m" | Month/day pattern | 6/15/2009 1:45:30 PM -> June 15 |
"s" | Sortable date/time pattern | 6/15/2009 1:45:30 PM -> 2009-06-15T13:45:30 |
"t" | Short time pattern | 6/15/2009 1:45:30 PM -> 1:45PM |
"T" | Long time pattern | 6/15/2009 1:45:30 PM -> 1:45:30PM |
"Y", "y" | Year month pattern | 6/15/2009 1:45:30 PM -> June, 2009 |
Returns TRUE where value1 is greater than value2.
Usage
greaterThan(value1, value2)
Returns TRUE where value1 is less than value2.
Usage
lessThan(value1,value2)
Returns TRUE where either logical arguments are true. Returns FALSE when both logical arguments are False.
Usage
or(boolean1, boolean2)
Returns the text component of the list item in the lookup control if condition evaluates to TRUE. If FALSE, returns the ID of the list item in the lookup control.
Usage
parseLookup([array or single lookup value], [optional bool showText])
Note: A lookup control returns both the ID and text for the selected items in the format "1;Australia". The first part represents the ID of the list item and the second part, the column specified to display in the lookup control as its label. Depending on what you are using the lookup control value for, you will need one part of the value.
e.g.
parseLookup(Country) = "Australia"
parseLookup(Country, true) = "Australia"
parseLookup(Country, false) = "1"
The lookup function allows a form designer to retrieve data from a column within a SharePoint list and display that data on a form or use it in a formula.
A common requirement among form designers is the ability to surface SharePoint data from another list and optionally process that data. Displaying an entire list item or a list view is possible with the List Item and List View controls respectively, however these controls render html as their output which cannot be processed in a Nintex formula. In scenarios where you want to obtain a value from a list column, for display or processing in a formula, the lookup function is a viable approach.
Within a Nintex Form, the lookup function can be used within a:
To understand how the lookup function determines what data to bring back, consider the following lookup function:
lookup(“listA”, “ID”, 1, “Title”)
This lookup will send a query to SharePoint, asking for list items within a list titled ‘listA’ and return the Title column value from any list items whose ID column value is 1.
Note: The match on the value is case-insensitive.
The lookup function does not support complex query construction; it determines what list items are included, as data to bring back, based on the filter column being an exact match to the value you specify. You can compose complex formulas with the formula builder if you need to build up a complex query, however be mindful that each lookup function will send an individual request to SharePoint for data.
list title: The title of list that contains the data you are querying.
column to filter on: The name of the column in the list that you want to filter on. Specifically, this column will be used to filter which list items are treated as matches against the third parameter.
value to filter on: The value you specify for this parameter is compared against each item in the list, if it matches the value for the column you specify in the second parameter, the list item data is returned.
output column: The name of the column in the list that you want to get data from. Data from the output column is returned in the formula.
multiple values <optional>: Used to signify that you want multiple values returned from the lookup function. This should be used if there are more than one list item which matches the filter you’ve configured and you want an array of values to be returned.
value data type <optional>: Use to manually set the underlying data type that SharePoint will compare your value as.
The list you are querying can exist within the current site, or within sites within the current site collection.
The following types of data are supported for the ‘value to filter on’ parameter:
Note: Null is a valid input value.
The lookup function does not currently support multiple values being passed in as the input value parameter. Only a single value is supported. I.e. you cannot pass an array of values into a lookup function.
The returned column value will not be formatted by the lookup function unless it’s one of the following SharePoint types:
For Example: Given a SharePoint Person column, the displayed value of a Person column in SharePoint may appear as “User A”, but the underlying SharePoint text is of the format “1;#UserA”.
If a lookup function is configured to return a Person column’s value, it will convert it into text, using the internal format of “1;#UserA”.
By default, the data returned from this function is for a single column in a list. You may want to return multiple column values: For example, where multiple list items matched a given query. To do this, append ‘true’, without the quotes, as the last parameter of the function. For multiple output values, they are returned inside an Array. An array is of the format [value1,value2].
You can use a Named Control, Item Property, Form Variable, Workflow Variable or a pre-defined property as the input value of a lookup function. All types of data to insert are listed in the Formula Builder dialog.
Note: Quotes are not necessary when inserting a control, property or variable.
The lookup function is dynamic; if any parameters that are passed into the function change during runtime, the lookup function re-fetches the data and triggers the formula to re-evaluate.
All lookup data is cached for 2 minutes to reduce network traffic.
All lookup functions are evaluated on load of a form, unless they are configured to not recalculate on view mode. This option is per control in the control property window.
Lookup functions are processed asynchronously, meaning they do not halt the form from operating while they fetch the SharePoint data and evaluate. This helps in scenarios where the network between you and the data is slow or physically far apart.
Lookup functions currently do not work in Nintex Live Forms.
Formulae that depend on other formulae containing a lookup function will not wait before evaluating. Consider the following scenario of two Form Variables:
Variable A has the formula: Variable B + 1
Variable B has the formula: lookup(“listA”, “Title”, “Task1”, “ID”)
Variable A depends upon Variable B, however an individual formula only waits until all endogenous lookup functions are complete before evaluating. The result is that Variable A will momentarily evaluate to ‘1’, as Variable B has not yet completed. When Variable B does complete, it notifies Variable A to re-calculate, at which time Variable A displays the complete value of: ‘<Variable B’s lookup value> + 1’.
If you have multiple, dependent lookup formulae and require all lookup functions to be complete before displaying a result to the user, utilize a single formula with nested or chained lookup functions.
The lookup function will perform the lookup of SharePoint data as the current user. Therefore, if the user filling out a Nintex Form does not have the necessary SharePoint access to the list or list item(s), the lookup function will not return any data.
Lookup functions can be nested inside of other lookup functions. Lookup functions will evaluate inside out, (for example, a lookup function inside another lookup function will evaluate first) to maintain formula correctness.
As a form designer, be mindful not to construct a formula which contains a circular reference. A circular reference is where a formula is dependent on another formula to complete, but that formula depends upon the original formula completing.
If a circular reference is accidentally configured, the lookup function will stop evaluating after a fixed number of cycles.
To help with troubleshooting issues, preview your Nintex Form and press F12 to open the IE developer toolbar. Next, click on the Script tab and ensure that the Console tab on the right is selected. Refresh your preview window by right clicking and selecting Refresh. Logging will appear in the window, and help you to troubleshoot common misconfiguration/data access issues.
To see an example of using the lookup function, refer to the guide ‘Lookup data from another list inside a Nintex Form' on Nintex Connect.
A form variable represents a hidden calculated value that can be referred to in other runtime expressions such as calculated value controls and rules and can also be bound to a column. Its value itself is determined by its own runtime expression.
Form variables provide the ability to manage values in a single location for use across your form without it having to be shown on the form canvas. They behave just like calculated value at runtime and can be bound to list columns without the need to be displayed in the form itself.
On the left hand side we present a list of all the form variables in your form.
The Form Variable form displays the following:
Selection | Description |
Execute Test | Verifies connection to an external system using the current configuration settings. |
Test Result | Displays the output of the executed test. |
Execute XPath Test | Verifies XPath configuration for a connection to an external system using the current configuration settings. |
XPath Test Result | Displays the output of the executed XPath test. |
Unsupported form configuration for PDF rendering
Form Configuration | Discription | Browser |
Rules | Custom CSS rule @Media rule. |
Only applies to Internet Explorer 8. |
Controls |
|
Applies to all browsers. |
Images | SVG images. | Applies to all browsers. |
The Nintex Forms Start Site Workflow web part is used to display a site workflow start form that was created using Nintex Forms.
To add a site workflow start form web part to a page:
Designing forms in Nintex Workflow
Getting started with the form designer
Configuring the List Form Web Part
The Nintex Forms List Form Web Part allows you to embed a list form designed using Nintex Forms on a page.
If Edit or Display is selected for the Form Mode:
If New is selected for the Form Mode:
To add a list form web part to a SharePoint page:
A List Form Web Part can be connected to a List View Web Part. This allows the user to easily edit or view an item in a list. When an item is selected in the List View Web Part, the List Form Web Part will display the item that was selected.
Note: The two web parts need to be on the same SharePoint page.
To configure the List Form Web Part as a connectable web part:
Note: A List Form web part may only be connected to one List View Web Part. To connect to another List View Web Part, the connected List View Web Part must be disconnected. To disconnect from the List View Web Part, open the List Form Web Part's drop-down menu and select Connections. Untick the connected List View Web Part.
When a List Form is set to Edit mode, the form may be edited in the SharePoint page. When a List Form is set to Display mode the form may only be viewed in the SharePoint page and cannot be edited.
To configure the List Form Web Part in edit or display mode:
Note: If the list has not been enabled for management of content types, in the Content Type/ID, type in 'Item'.
When a List Form is set to New mode, a new List Form will appear when the SharePoint page is accessed.
To configure the List Form Web Part in new mode:
Note: If the list has not been enabled for management of content types, in the Content Type/ID, type in 'Item'.
Getting started with the form designer
Configuring the Start Site Workflow Webpart
Nintex Forms supports designing the form of a SharePoint external list (External Content Type). For more information on SharePoint External List (External Content Type), refer to http://msdn.microsoft.com/en-us/library/ee558737.aspx.
Note: When designing a Nintex form for a SharePoint external list, the form designer has the ability to change the controls of the external data columns which otherwise would have limited users to just a single line textbox when using the out of the box SharePoint external list.
Getting started with the form designer
Designing forms in Nintex Workflow