Introduction to Nintex Workflow for SharePoint

One of the most powerful features in SharePoint that doesn’t get used nearly as often as it should is workflow. One of the reasons for this is that many people are just intimidate by it. They might use some “Out-of-the-Box” approval workflows but beyond that the idea of creating a custom workflow is seen as beyond their capabilities. This is why we have partnered with Nintex. They have a workflow product that integrates seamlessly into the SharePoint user interface so it does not require using Visual Studio or SharePoint Designer. Nintex Workflow provides an intuitive visual interface that makes creating and maintaining workflows much easier.

Over the course of the next few weeks I will be writing a series of articles going through a number of common features that every business can benefit from. The workflow I am going to create during this series of articles is just a simplified example of something you might run into. I am going to have the workflow manually started so it can have a start form to collect data. The workflow is going to assign tasks to 3 different types of approvers in parallel. The approval process will be the same for each but the notifications that will go out to each group will be a little different. This will allow me to show you creating a parallel process and create a user defined action. Additionally I will show how to loop back in case the Project Manager wants to resubmit a Declined tasks to the approver.

For this article I will start from the beginning and show how to customize the workflow start itself by creating variables and customizing the start form.

Let’s get started from the beginning. You will want to start in a list or library, in my case I am starting out in a document library. So we will go to Workflow Settings and select “Create a Workflow in Nintex Workflow”.

When prompted I selected a Blank Template for my workflow. At this point you will see a screen that is similar to flow chart in Visio. The Actions are on the left and the flow chart is in the main part of the screen. At this point I am not going to add any actions I will do that later. In the ribbon click Workflow Settings.

In the Workflow Setting screen, enter a Title for your workflow, a Description of the purpose of the workflow and select the workflow options that you require, in this case I have select Start Manually, and set Start when items are created and Start when items are modified to “No” so that I can have a custom start form.

 

Now we can add some variables to be populated on the start screen. In the ribbon click “Variables”.

 

I am going to create a few person selector fields, 3 Approvers and a Project Manager. In the Workflow Variable screen click New and then give the field a Name, select “Person or Group” for the Type, Select “Show on start form”, Select “Required”, and I am choosing “Any User” and “Allow Users” but you can set these however you want.

 

After doing this for all 3 Approvers and a Project Manager and adding an Approval Text field (Single Line of Text) your Workflow Variable screen should look like this.

 

At this point, you can Close the Workflow Variables screen. We are now going to customize the Start Form so click the drop down arrow on the Edit Start Form button in the ribbon and select Edit with Nintex Forms.

 

This will bring up the Nintex Forms – Form Designer. From here you can make whatever changes you would like to the Start Form. For now I just changes some label and made a few other minor changes.

 

Click Save and then Click Close. Click Save in the Workflow Setting screen. Now we will add just a simple logging action so we can publish our workflow and test the new Start Form.

Log in History List is located in the Operations Group so either open that group and on the left and drag the Log in History List action to the open square in the workflow or right-click on the square and select the action from there.

Notice the exclamation point in the Log in history list item once you have placed it in your workflow. This indicates that you need to do some configuration on that action. Click on the drop down arrow on the action and select Configure.

You can enter any text you want in the text box and insert variables and meta-data values from the associated list item. In this case I just want to log who the Project Manager is. I type the text “The Project Manager for this is: ” and then click the Insert Reference button. Notice the tabs at the top that give you several different options for the source of the information to insert. Click the Workflow Variables tab and then select ProjectManager and click OK.

 

Click Save and you should now see that the exclamation point has gone away. Now we have a very simple workflow that we can publish. Click the Publish button in the ribbon, enter any Change Comments and click Submit. After the workflow has published you can click the Close button in the ribbon to exit Nintex Workflow. If you now go back into the list/library in which you created the workflow and add an item or upload a file we can test the workflow. Click the drop down arrow on the file name and select Workflows.

 

Click on the workflow you just created.

 

You should see the Start screen that you created. Select users for the 3 Approvers and the Project Manager and add some Approval Text and click Start. You can then go into the Workflow Information screen by clicking the drop down arrow next to the file name, selecting Workflows and then Clicking on your workflow in the bottom section “Completed Workflows”.

 

You should now see in the workflow history section and event with a description that tells you who you selected as a Project Manager.

 

Just to recap, in this blog post I showed you how to create a Nintex Workflow, Set some basic properties, Add Variables, Edit the Start Form, Add and Configure a basic Action, Publish and run you workflow. In my next blog posts I will continue to build upon this workflow in order to demonstrate some more advanced functionality of Nintex Workflow.

11 comments

  1. Bob H. says:

    Thanks so much for taking your time to document and post the information regarding Nintex Workflow. We are considering this product and your posts are very helpful!

    Bob H.

    • Brian Zebarth says:

      Thank you for your comment. Nintex is a great product and can be a real time saver. I am hoping to have time in the next few weeks to continue this series of posts.

      If you think you might want some help with implementing Nintex and getting started with some workflows click the Contact link at the top.

  2. LorettaO says:

    This is very helpful. I want a start form that will capture data from an end-user and then run a approval workflow from there. These steps you’ve provided require a record to be added to a list/library first and then to manually launch the workflow. How can I get these 2 steps to process together [i.e. not require someone to manually start the workflow]

    Ultimately I want to use a Nintex start form to gather data from the user, but then use standard out-of-box SP to edit or review those list items?

    • Brian Zebarth says:

      Thank you for your question. If I understand what you are asking you cannot both use a Nintex start form and have the workflow start automatically. You can set the workflow up to start when a new item is added or when an item is updated on the Workflow Settings page by selecting Yes for “Start when Items are created” or “Start when Items are modified” but then the start form will not be used.

      Depending on your exact needs, you could add columns for the information you want to collect from the user to the library/list and use a custom InfoPath or Nintex form to collect that information from the user when creating a new item. Then if the workflow is set to start when an item is created you could access those item fields from within the workflow.

      If you need additional help feel free to reply again or click the Contact link at the top.

    • I completely agree with the fact that if you do not know all the processes, you can not use the program at full capacity and benefit from it.

  3. Achint Kishore says:

    Hi Brian

    Thanks for the nice article. Can you please brief me about the Nintex architecture or can you please pass on any link that explains about it?

    Your help will be highly appreciated.

    Thanks

    Achint

  4. shardul says:

    Hi,
    I able to set start page for nintex workflow to “_layouts/IniWrkflIP.aspx” as it was our custom code requirement. Is there any drawback or downside of this?
    Thanks in advance

    Thanks and Regards,
    Shardul Pasare

  5. sai krishna says:

    Hi Brian,

    I have a problem in scheduling a workflow i.e, there’ll be a decision box in the workflow and depending on the decision i.e, YES or NO i need to schedule it for every 12 months or every 3 months depending on the decision whether its YES or NO.I know that we can schedule a workflow only once with a time period but how can we can we schedule it in two different time periods in a single workflow??can u please help me regarding this issue..

    Or else we should use loop concept to achieve this.If Yes then how can i achieve it.A detailed explanation will be more helpful?

    Thanks,
    sai

  6. Bijay says:

    Seems to be very nice tool… will surely recommened some of the clients.

  7. Holly says:

    Wow, you have no idea how helpful this is. My office is overhauling a massive Nintex workflow which was created solely by departed personnel…and no documentation. This situation combined with the fact that it is hard to find Nintex tutorials has made my job real tough.

    Your blog is so appreciated. It brings me a lot closer to figuring out what to do about this. THANK YOU!

  8. Suzanne says:

    Thanks for the article. I am using Nintex but I don’t have Edit with Nintex Forms. I have Infopath 2013. I followed your procedures but the approvers did not receive e-mails requesting them to approve.

Leave a Reply

Your email address will not be published. Required fields are marked *

J49U JR4fVp sa

Please type the text above: