Skip navigation
All Places > Getting Started > Blog > Authors pamela.denchfield

Getting Started

7 Posts authored by: pamela.denchfield Employee

This tutorial describes how to enable a scenario for "deep linking" to automatically submit scanned codes using Nintex Mobile. The tutorial also describes the user experience when accessing the link through the QR code.

 

Forms designer steps

This section describes how to enable the scenario in Getting even deeper linking with Nintex Mobile and Nintex Mobile Enterprise by creating Nintex Mobile links to log confirmations for a security protocol. The process for enabling this scenario involves creating the form, bulding the links for each door, generating the QR codes for the links, and implementing the security system.

 

The Nintex Mobile links in this tutorial do the following:

  • Customize the loading message so staff members know that the Security Check form is loading
  • Point to the Security Check form
  • Pre-populate the Title field with the door name
  • Enable automatic submission of the form
  • Enable display of the successful submission message so staff members know that the scanned QR code was successfully submitted

 

To create the form:

  1. On your SharePoint site, create a list named "Security Check" and add a column named "Checkin" using the type Date and Time with the default value of Today's Date.
  2. In Nintex Forms designer, add the Nintex Mobile layouts and then publish the default form.

 

To build the links for each door:

  • Use the following examples based on the door names Back Roller Door East, Back Door West, and Front Door.


nintexmobile://form?ntx-name=Security%20Check&Title=Back%20Roller%20Door%20East&ntx-autosubmit=true&ntx-msgLoading=Loading%20Security%20Form&ntx-msgSuccess

 

nintexmobile://form?ntx-name=Security%20Check&Title=Back%20Door%20West&ntx-autosubmit=true&ntx-msgLoading=Loading%20Security%20Form&ntx-msgSuccess


nintexmobile://form?ntx-name=Security%20Check&Title=Front%20Door&ntx-autosubmit=true&ntx-msgLoading=Loading%20Security%20Form&ntx-msgSuccess

 

To generate the QR codes:

 

To implement the new security check system:

  1. Print out the QR codes and affix them to the appropriate doors.
  2. Make sure all staff have the Nintex Mobile app and a QR reader on their phones

 

User experience

This section describes the user experience when accessing the above Nintex Mobile links.

 

  1. The staff member uses the QR reader app on the phone to scan the QR code on the door.
    The customized loading message briefly appears: "Loading Security Form."
    If the staff member is not logged into the Nintex Mobile app, then the sign in screen appears.
  2. If needed, the staff member signs in to the Nintex Mobile app.
    The default message for a successful form submission appears, indicating that the Security Check form was successfully submitted with the QR code.
  3. The staff member dismisses the message.

 

For more information about Nintex Mobile links, see the Nintex Forms for Office 365 help.

This tutorial describes how to use range and regular expression validation in Nintex Mobile, using a lead generation scenario for validating entries of email addresses and follow-up dates. In this scenario, email addresses are validated for inclusion of the "@" symbol and a period; follow-up dates are validated for occurring within three months of the trade show at which the forms are filled out. The trade show is occurring in August 2016.

 

To achieve this scenario:

  1. Create a SharePoint list called "Leads" and add the following columns: Name, Region, Email, Phone, Followup date.
  2. In Nintex Forms designer, double-click the Single Line Textbox control for Email.

  3. In the form control configuration dialog box, expand the Validation section and then select Yes for Use a regular expression.
  4. In the Regular expression field, copy and paste the following expression.
    .+\@.+\..+
  5. In the Regular expression error message field, copy and paste the following text or enter a similar message.
    Invalid format for email address. Please reenter.
    Example screenshot of validation configuration:

  6. Click Save to save changes and close the configuration dialog box.
  7. In Nintex Forms designer, double-click the Date/Time control for Followup date.

  8. In the form control configuration dialog box, expand the Validation section and then select Yes for Use range validation.
  9. In the Minimum value field, insert the reference "Current Date."
  10. In the Maximum value field, specify a date occurring several months after the trade show.
    Example: 2017/01/01
  11. In the Range validation error message field, copy and paste the following text or enter a similar message.
    Please enter a date in the future.
    Example screenshot of validation configuration:

  12. Click Save to save changes and close the configuration dialog box.
  13. Add the Nintex Mobile layouts and then publish the form.
    Now the form displays errors if users attempt to submit with an email address or followup date not passing validation.

Nintex Forms Enterprise Edition

 

This tutorial walks through steps to retrieve country and city data from a SQL Server database and filter the returned city data based on the selected country.

Figure: Example of a form listing cities for the selected country; if another country is selected, the list of cities is updated.

 

Prerequisites:

  • Database table "Cities" containing two columns: Country and City
    Example:
  • Secure Store target application ID for credentials to the SQL Server database
    For more information on Secure Store, see the Microsoft article Configure the Secure Store Service in SharePoint 2013.
  • List columns for binding the value and display fields for each instance of the SQL Request control (optional)

 

Steps:

  1. Add the SQL Request form control for "Country" and apply the following configuration.
    FieldValueNotes
    NameCountry
    Display formatDrop down list
    Query typeSQL
    Query

    SELECT [Country]

    FROM [CrestanDemoData].[dbo].[Countries]


  2. Add the SQL Request form control for "City" and apply the following configuration.
    Note: Red text indicates inserted references.
    FieldValueNotes
    NameCity
    Display formatDrop down list
    Query typeSQL
    Query

    SELECT [City]

    FROM [CrestanDemoData].dbo].[Cities]

    WHERE Country='Country'

    To insert a reference to the "Country" control, select it from Named Controls in the Insert Reference dialog box.
  3. Publish the form and you're done!

Nintex Forms Enterprise Edition

 

This tutorial walks through steps to display current wind direction for the city selected on the form. The tutorial uses the Web Request form control from Nintex Forms Enterprise Edition to send a GET request to the Yahoo weather API (anonymous authentication), filtering based on the city selected on the form (ChoiceField).

 

Figure: Example of a form displaying wind direction for London; if another city is selected, the wind direction is updated for that city.

 

Prerequisites:

  • List column WindDirectionID for binding the XPath value field
  • List column WindDirectionText for binding the XPath display field
  • Choice control “ChoiceField” with valid values for cities referenced by the API (example follows)
    • Casablanca
    • London
    • Melbourne
    • Paris

 

Once you have the above prerequisites, add the Web Request form control to the form and apply the following configuration. Publish the form and you're done!

Note: Red text indicates inserted references.

 

Field

Value

Notes

Name

WindDirection

 

ID connected to

WindDirectionID

 

Text connected to

WindDirectionText

 

Display format

Label

 

Service URL

https://query.yahooapis.com/v1/public/yql?q=select wind from weather.forecast where woeid in (select woeid from geo.places(1) where text='ChoiceField')&format=json

To insert a reference to ChoiceField, select it from Named Controls in the Insert Reference dialog box.

Request method

GET

 

Authentication type

Anonymous

 

XPath for display

//direction

 

In Nintex Workflow for Office 365, use dictionary variables for the “Field names” and “Field values” selections shown in the action configuration settings dialog box for DocuSign Populate Template.

 

DocuSignPopulateTemplate-O365-FieldNamesFieldValues.png

 

When building dictionaries for names and values, key each dictionary identically; that is, use the key of the name (first dictionary) for the corresponding key of the value (second dictionary). In the example dictionaries below, the key “(0)” is used for both “Date Applicable” (FieldNames dictionary) and {Current Item:Modified} (FieldValues dictionary).

 

Example FieldNames dictionary:

Key

Type

Value

(0)

Text

Date Applicable

(1)

Text

Full Name

(2)

Text

Subject

 

Example FieldValues dictionary:

Key

Type

Value

(0)

Text

{Current Item:Modified}

(1)

Text

{Current Item:FirstName} {Current Item:LastName} of {Current Item:Company}

(2)

Text

{Current Item:Subject}

 

For more information about this workflow action, see DocuSign Populate Template in the Nintex Workflow for Office 365 Help.

 

For comparison to Nintex Workflow 2013 and Nintex Workflow 2010, see the workflow described in Nintex Connector for DocuSign.

Products: Nintex Forms for Office 365, Nintex Forms 2013, Nintex Forms 2010

 

Symbols and meanings for rules in Nintex Forms are provided below.

SymbolMeaning
==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

 

 

Did you know that this information is provided in the product Help files? The Help files contain useful information for writing rules in Nintex Forms. Simply click the Help button in the Designer tab to see context-sensitive help. Below is an example of the Help button from Nintex Forms for Office 365.

Help-NF0365.png

 

You can also access Help online. Below are links to information on rules by product.

Nintex for Office 365 | Nintex for SharePoint 2016 | Nintex for SharePoint 2013 | Nintex for SharePoint 2010

Products: Nintex Workflow for SharePoint (2016, 2013, 2010)

 

Avoid “All” and “Item” Content Types

 

To prevent lengthy content type evaluation when saving or publishing reusable workflow templates, avoid selecting “All” or “Item” for the content type. Instead, create a content type based on Item and then select the created content type when defining the reusable workflow template.

 

For instructions on creating content types, refer to the SharePoint documentation.

 

More Information

 

For more information about reusable workflow templates, see “Set Title and Description for Reusable Workflow Template” in the Nintex Workflow Help (2016 | 2013 | 2010).

 

For more information about the evaluation process that Nintex Workflow uses for content types, see the following MSDN article: http://msdn.microsoft.com/en-us/library/office/microsoft.sharepoint.spcontenttypecollection.bestmatch

Filter Blog

By date: By tag: