Skip navigation
All Places > Getting Started > Blog > 2015 > June

Please refer my previous article to learn more about creating NINTEX workflow in SharePoint 2013 Online.

In this blog you will see how to remove group using NINTEX workflow in SharePoint 2013 Online.

We will be removing the group from SharePoint site by calling the web service _vti_bin/usergroup.asmx. I have created a list which contains Name – Single line of text andComments – Multi line of text field.

Workflow Design:


Web Request Action:





Soap Action:


Set Field in Current Item Action:


The group name specified in the "Name" field is removed successfully from the SharePoint site.


Please refer my previous article to learn more about creating NINTEX workflow in SharePoint 2013 Online.

In this blog you will see how to remove user from group using NINTEX workflow in SharePoint 2013 Online.

We will be removing the user from SharePoint group by calling the web service _vti_bin/usergroup.asmx. I have created a list which contains Name – Single line of text,UserLoginName – People picker and Comments – Multi line of text field.

Workflow Design:

Web Request Action:

Soap Action:


Set Field in Current Item Action:


The specified user is removed successfully from the specified SharePoint group.


Please refer my previous article to learn more about creating NINTEX workflow.

We will be adding the user to SharePoint group by calling the web service _vti_bin/usergroup.asmx. I have created a list which has Name – Single line of text, UserLoginName – People picker and Comments – Multi line of text field.

Workflow Design:

Web Request Action:

Soap Action:

Set Field in Current Item:


The specified user is added to the specified group successfully.


In this video from Sean Fiene, he explains how to manage and optimise rules in the forms you create with Nintex Forms for SharePoint.


Nintex VP of Workflow Technology Mike Fitzmaurice, shows you how to use batched actions, and committing changes in Nintex Workflow for SharePoint.


In the video Nintex Tech Evangelist Sean Fiene explains how to optimize the performance of your forms in Nintex Forms for SharePoint.


From Nintex Tech Evangelist Sean Fiene. In this video he explains how to hide controls in the forms you create with Nintex Forms for SharePoint by using panels and display rules.


Going on with the list of custom actions started on List of Nintex Workflows Custom Actions - Part 1  , here you can find more actions of any kind for Nintex workflow.


You are free to participate on these post collaborating with this list.





Simple and useful. This custom action is capable to run powershell commands.





BisCom Fax


Collaboration Greatly Simplifies the Routing of Incoming Faxes into Nintex Workflows and the Sending of Outgoing Faxes from Nintex Workflows


Not free. Unknown




A PDF Converter for SharePoint ships with a large number of Workflow Actions for both SharePoint Designer and Nintex Workflow 2007, 2010 and 2013.


USD 1,500




is it possible to hide the column that gives you Information about the actual action of the Workflow in the global Task-Webpart?

I want to prevent that users click the entry in that column an get into the status-overwiew of the actual workflow...


2015-06-17 09_41_13-tost Win8.png


it´s the last column in this screenshot "Aktuelle Aktion". It can´t be hidden by Webpart-Configuration.


Thank you for any hint!



This is the second video that I produced to help me progress in my Nintex Forms for O365 learning journey. This video covers how to add a form to a list and provides an overview of the basic product functionality, navigation, and user interface. Hope you find it useful. Enjoy!



<-- Previous: Fundamentals of Nintex Forms for O365 Video 1



Dean Virag

It is well known  that you can use or create your own custom actions to be used on our workflows.

I'll try to research about all kind of custom actions, that perhaps could useful on some of our workflows.

You are free to participate on these post collaborating with this list.




This is a sample to create a custom action so as to log exceptions on ULS.


Free. Developer skills needed.





WAND, Inc., a provider of taxonomies and the DataFacet Automatic Tagging Solution for SharePoint, has announced its integration with Nintex Workflow.


Not Free. U$S ?





CoSign connector can be used within a Nintex designer as a custom action, or as a “custom task” in a Nintex “to-do” task. Within Nintex workflows:

AutoSign with CoSign and Verify with CoSign are custom actions.

Signing with CoSign is a custom task that can be used within a native Nintex To-Do task.


Not Free. U$S ?





ERPConnect Services simplifies the integration of SAP data into your SharePoint solution. Customers that use Nintex Workflow in their SharePoint environment can utilize ERPConnect Services to access data in their SAP system..


> U$S 6,000



Get ListItem attachments


This custom action is capable to get attachments from a listitem.




Hi all. I am very new user to Nintex Forms and Workflows for O365. As part of my learning process I like to create videos of topics as I learn them. It helps me to master content, one small chunk at a time. I would like to share my videos with the Nintex Community. This first video is a foundation setting video on Nintex forms for O365. It is designed for users with little to no experience working with forms. It presents the terms and concepts that will be used in later videos. Let me know if there are topics you would like to see presented. Enjoy!


-- Dean



Next --> Fundamentals of Nintex Forms for O365 Video 2

I thought this would be helpful to share with other Nintex Users,


The original question that I was asked was how to remove the Claims token prefix before a username.


The solution is pretty simple, you can use the "Regular Expression" action within a Nintex Workflow and look for the pattern:




This will effectively remove the token, leaving you with just the domain\username.

Products: Nintex Forms 2010, Nintex Forms 2013


A question came in about activating Nintex Forms 2010/2013 via PowerShell. It is fairly easy to do assuming you have the FeatureDefinitionID (0cdf436f-61b0-43d2-b250-4360f0353b63). Below you will find an example for how to activate/deactivate the feature via PowerShell.


PowerShell Script
  1. Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
  2. Enable-SPFeature -Url -Identity 0cdf436f-61b0-43d2-b250-4360f0353b63 -Confirm:$false
  3. #Disable-SPFeature -Url -Identity 0cdf436f-61b0-43d2-b250-4360f0353b63 -Confirm:$false


Note: To deactivate the feature, uncomment the 5th line and comment the 3rd line.


Version History and other scripts can be found here:

Products: Nintex Workflow 2013, Nintex Workflow 2010


A request came in a few days ago for a way to programmatically toggle Nintex Features for all Site Collections\Sites that utilize Nintex Workflow in a given Web Application


This PowerShell script will disable and then re-enable all Nintex Features in the WebApplication (as long as they were previously enabled).


PowerShell Script
  1. Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
  2. $NWSiteFeature = '0561d315-d5db-4736-929e-26da142812c5'
  3. $NWWebFeature = '9bf7bf98-5660-498a-9399-bc656a61ed5d'
  4. foreach($feature in $(Get-SPWebApplication -Identity[Guid]$NWSiteFeature)){
  5. Write-Host "Processing $($feature.Parent.Url)"
  6. Disable-SPFeature -Url $feature.Parent.Url -Identity $NWSiteFeature -Confirm:$false
  7. Enable-SPFeature -Url $feature.Parent.Url -Identity $NWSiteFeature
  8. foreach ($webFeature in $feature.Parent.QueryFeatures([Guid]$NWWebFeature)){
  9. Write-Host "Processing $($WebFeature.Parent.Url)"
  10. Disable-SPFeature -Url $webFeature.Parent.Url -Identity $NWWebFeature -Confirm:$false
  11. Enable-SPFeature -Url $webFeature.Parent.Url -Identity $NWWebFeature
  12. Write-Host "Completed $($WebFeature.Parent.Url)"
  13. }
  14. Write-Host "Completed $($feature.Parent.Url)"
  15. }

To use the script do the following:

  • Replace with the URL of the WebApplication you wish to execute the script against.


Version History and other scripts can be found here:

Have you ever needed to document your workflow, and if so, how have you done it? This post was generated from the discussion Did you ever need to document your workflow?


You'll find a summary of the suggestions our members have on how they document their workflows. Feel free to continue leaving comments below with any of your own suggestions, and let us know if you also use some of these ideas.


The importance of documentation


From Mike M

You really can't go wrong as long as your documentation tells the story that is required to be told. I would say that the documentation that I've had to write depends greatly on the complexity of the workflow, as well as what would help the customer best understand the workflow/business process at hand. This often includes a mixture of text with screen shots captured of the most important parts of the workflow (or sometimes the parts least likely to be understood).




From Rency Gonzalez


What I have done is used snagit to take screenshots and then paste it into a word document. With Snagit you can crop and add call outs or arrows to the screenshot using the Snagit tools.  Next to the screen shot you could possibly add a few bullet points on what the actions are doing. I attached a sample screenshot of what I have in my workflow document. I hope it helps.sample wf.png


Use the Print functionality in Nintex Workflow

From Christof Meyer


There are two options to print a Nintex workflow, one is Print only and one is called Print with Notes.

When you configure an item, take the tab "labels" and in the section: "Notes to display", choose User defined and write your comment in this




When you print it, you can see your comments below the workflow. With big workflows, you should split in Main- and subworkflows not only for readability. Further information: Breaking up a large workflow, to split or not to split? Approach to splitting a Nintex Workflow  Defensive Workflow Design Part 3 - Separation of Concerns


Visio and Excel

From Andrew Glasser


When my audience is less technical I almost always use visio to document the process of the workflow. Visio also helps when designing a workflow before build with technical teams as well. Then once it is built we can review using the screen captures or print outs of the workflow itself from the Nintex Designer with notes.


Many times I use Excel to supplement some areas that need to be documented. Such as notifications and tasks. With Excel we will map out the different components of the notifications. Like Subject, Body, and assigned to. This is very useful when building a workflow that has many notifications. But may not be necessary for a simpler workflow.


Eric Rhodes also uses a combination of Visio and Excel with Action Labels to document workflows.


I work with clients to document the "business process" side of the workflows with Visio.  This allows the client map out the entire process to better understand and document how everything currently works.  This also helps to distinguish between automated and manual (non-workflow) processes.  A key component of this diagram is providing a numbering system for each task that corresponds to an automated action in the workflow.


Documenting the task and notifications in an Excel spreadsheet is a huge help.  The spreadsheet includes components like task name, task details, task assignees, email subject, email body, and email recipients.  This allows clients to really think about and plan out how tasks and notifications are laid out.  These details are often overlooked and cause headaches down the line.  The spreadsheet also serves as a good future reference point and easy way for users to make changes.  I also use the numbering system from the Visio diagram to link actions together.



From Aaron Labiosa


Pairing up the opensource tool Greenshot with Workflow Analyzer is what I like to use for documentation/ annotation of workflows.


Workflow Analyzer

Aaron Labiosa 's tool named "Workflow Analyzer" has some useful features that could be used for documentation. Take a look at >>> Workflow Analyzer - Initial Beta Release


Labelling the Workflow Actions


From burkslm and Eric Rhodes

  • Update the labels in the actions. You can just change the text in the actions. That has been good enough for me.
  • I suggest using the action labels in the workflow designer to document workflows. I typically use a descriptive title in the Action Title label, the corresponding number from the numbering system in the Left or Right Text label, and the action assignee or recipient in the Bottom text label.  This systems helps workflow users or designers quickly understand details about each action.
  • How to set the workflow action labels


Leave any comments in the section below.

Hello Everyone!


Today we're introducing a few new changes to the Nintex community site. These changes are focussed on the top navigation piece, as well as your activity streams.


Top Navigation

You’ll notice that there is an additional tab in the top navigation called “News”. When you click on News it’ll take you directly to the activity stream of the site.


Once you’re in the News Stream, you’ll see options for different kind of streams. By default your news stream will show content which is targeted to you with a focus on trending activity, trending people, recommended content, people and places.


There is also a Top and Trending, and Most Recent stream.


Top and trending


The “Top and Trending” space will show you the top content in the Nintex community. When you return to this stream, you’ll see a blend of content you may have already seen, as well as recommended content you may have missed.


Most Recent


The “Most Recent” stream is a time based activity stream which provides updates on any updates to documents or blog posts, new discussions, or new content that has been created.


Creating your own streams


You can also create your own streams of activity. This may be on a space, certain people, or a tag. For an example of how to create your own activity stream, go to Customizing your Community Activity Stream


Where is my inbox?

Your inbox is now accessible directly from the navigation at the top of the screen. You’ll recognise it by the @ sign. Clicking on the @ icon will take you directly to your inbox.


How to access My Content?

Accessing your content is now easier than before. To access your content, including questions you have posted, blog posts you have written, questions you have responded to, or any content you have saved in drafts, click on Your Content.



How to I access my bookmarks?

You can access your bookmarks from the search bar, or from your profile. This post Community Tip - Locating your saved bookmarks explains how that's done.


Changes to viewing content on Nintex Connect

The Nintex community has areas which are visible publically without signing in, and other areas which you will need to be registered on the stie to view content. Make sure you're signed in to access all the content on the site


I've put together some of the common licensing questions we see in the community.


How do I find my licensing information?

This post Nintex Licensing Information shows you two ways of accessing your licensing information; either through the designer, or through SharePoint Central Administration.


How do I import a new license for Nintex Workflow or Nintex Forms?

There may be times when you need to update your product license. This document shows you how to do just that Importing a license / Adding new servers.


What happens if I'm adding new servers to my farm?

If you're adding new servers to your farm, please request a license update from the Nintex Licensing team ( incorporating the new server name, and then import the license as described in this post Importing a license / Adding new servers.


What is the difference between Registered (Enterprise) and Development (Enterprise) license type?

A Registered (Enterprise) license is the Production license. A Development (Enterprise) license is the Development/Test/Stage/QA license.


Does a production license expire?

A production license does not expire, even if the Software Assurance on the license has expired. However, without current Software Assurance, you will not be able to update to the latest Nintex software, or receive Technical Support.


Development licenses are tied to Software Assurance, and do expire. If your Software Assurance expires on your development license that license will no longer function.


What is Software Assurance?

Nintex Software Assurance provides email and live support via chat to assist with installation, configuration and technical troubleshooting. One non-production license is included in each production license purchased as part of your valid Software Assurance.


How do we migrate, and what does Nintex offer?

All active Software Assurance customers are entitled to version migrations (e.g. Nintex Workflow 2010 to 2013). Version migrations include Development licenses at no additional cost as long as the Software Assurance contract remains valid throughout the migration, for up to 12 months.


Once the new version environment is complete on the development server, a 15 day temporary production license will be issused to complete the migration process. All migrations requesting to run parallel production environments will be required to purchase additional production licenses. Before you migrate please see Migrating/Upgrading - What you need to know


I've updated my server with the new license, but my site still shows the "Expired" red message

One of our members had this problem, and posted his solution here Updating Licenses. An ISS Reset was required.

Nintex Forms allows a Forms Designer to set conditional formatting and validation within their task form using the outcome values (Approve, Reject and the other custom outcomes) the form designer may have made in the Flexi-task action.


For information on how to configure the Formatting Rule, please read the following post: Using validation rules to ensure a comments box is not left empty


However, one question that comes up is, why is the Formatting/Validation rule written around an outcome equaling a number and not the value 'Approve' or 'Reject'?


For example, in a Nintex Task Form, you may see a Validation or Formatting Rule that looks like this:



Well, what is the '1' that we are talking about?  Why not the term 'Approve'?


In the Nintex Workflow Config database, you will find a table called 'dbo.ConfiguredOutcomes'. That table stores the Id as well as the associated Name for the outcomes used in the 'Decision' control of the Nintex Task Form.




When writing a Formatting/Validation rule on a Nintex Task Form, you will want to use the 'Id' of the appropriate outcome. You can also see the outcome by adding a Calculated Value Control to your Nintex Form, and assigning the value of the Calculated Value control to that of the Named Control 'Decision'. Once the form is used in a workflow, you will see the 'Id' number appear in place of the Calculated Value control.

Some users that use the International version of Nintex forms, use to show the designed form on the Nintex Form Web Part.


On those cases when a user saves a form, they see the following message: "Item added succesfully" , that is not a message in their language.


Here is a workaround so as to change that message:


Add the next sentece on the Form settings, custom Javascript section.


NWF$("span:contains('Item added successfully')").html('Vare tilføjet med succes');


So… virtual show of hands, who here knows what the Connection Manager is? If you do, well done!


What is it?

The Connection Manager is a simple way to manage connections to external providers through the Workflow Designer.


The current providers we have available are:

  • DocuSign
  • Microsoft Dynamics CRM
  • Salesforce


Where is it found?


In the Nintex Live Section of the Workflow Designer Ribbon (Nintex Workflow 2013 / Nintex Workflow 2010), you will see an icon for the Connection Manager.


Why is this GOOD?


Back in the day (prior to the Connection Manager), a user had to enter the account used each time they wanted to fire off an action that required some sort of authentication. (GROSS!)


With Connection Manager, you can store the credentials to be used for those External Provider actions (DocuSign, CRM, Salesforce). (HOORAY!)


Even Better… (this is important)


When setting the Connections up, you can scope it two ways:

  • User: Limits availability of this connection to the current user account.
  • Site: Does not limit availability of this connection. Any user on the site can use the connection.


Want to get your orange(black) belt in Connection Manager?


Read this:

This post applies to Sharepoint 2013 on Premise and Nintex Forms. I have not tested it on another versions, but I think it‘d happen the same.

Currently you can use a formula on the “Calculated Value” control available on Nintex Forms.

There is a particular behavior when you compare two columns of type person.


The case that works as expected


I have 2 columns of type Person named PrimaryOwner and SecondaryOwner.

Both of them are equally configured.


Sharepoint List Configuration

Nintex Form Configuration

And then I use the control named “Calculated Value” that has a formula on a Nintex form comparing those 2 fields.


The result


Then I added an item on the Sharepoint List setting those 2 columns with the same user.

With those values the result of the calculated value is true.

So far, so good.


The case that doesn’t works as expected


I have the same 2 columns of type Person named PrimaryOwner and SecondaryOwner.

Both of them are NOT equally configured. The difference is that I changed the property named “Show field” on the Sharepoint list settings for 1 of the columns.


The result


Without changing the saved values on the columns named “PrimaryOwner” and “SecondaryOwner” now the result of the calculated value is false.

I also tried using the runtime function named userEquals, but got the same results.

I do not know if it is considered a bug, but perhaps users expect that the comparison does not depend on the format of the field.

The current suggestion is to be careful when you use the Calculated Value control comparing columns of type Person.

I’ll try to talk with the support team so as to know their opinion.

Filter Blog

By date: By tag: