Managing (Show/Hide) columns shown in the Item Properties displayed on a Nintex Task Edit Forms


How to show/hide specific columns in the ‘Item Properties’ panel displayed in the Nintex task edit form?



In Global Settings for Nintex Workflow in Central Administration, there is a setting called Task form properties view – the default value is Workflow Task View.

If a view of this name is found on the list or library the workflow is running on, then only the fields specified in this view will be displayed in the item properties panel.


A Nintex workflow task approval form has an Item Properties section that will show all the columns from the current item in a list/library from where the workflow is running.  When you have more columns / don’t want to show specific column from the current list item in the Item Properties panel you can show or hide based on our requirement.

To do that follow the below steps:

  • Go to the list/library where the workflow is attached.
  • Open and modify the “Workflow Task View”.  If this view does not exist, create a new view with the name “Workflow Task View”.
  • Add or remove the necessary columns, then click OK to finish.

The Item Properties panel on workflow task edit form will now display the columns in the Workflow Task View.


Important Notes:

  • In the Item Properties Panel, we cannot remove / hide the “Workflow Status” column and it will be the first item in the Item Properties panel.
  • Workflow Task View has to have at least one column in the view.

How to open custom page / SPList item edit page when user clicks on Tasks item link?


When the user clicks on any of the workflow tasks list item created by Nintex Content Type, it takes to the Nintex approval page for approving/rejecting.  I would like to open the actual SP list item for which the workflow task is created instead of the default Nintex WF task list item or to open a custom page with query string values


Item name URL: Specifies where the user is direct to when they click on the list item name in the web part. 

  • Task display form: Directs to the view page of the task item. Please note: The default view form for ‘Request approval’, ‘Request review’ and “Assign a Flexi task’ has the same behaviour as the edit form.
  • Task edit form: Directs to the edit page of the task.
  • Item display URL: Directs to the item that the task is associated to.
  • Custom: Specify a custom page to direct to. The following place holders can be added to the query string:

{TaskListID}: The GUID of the task list.

{TaskID}: The ID of the task item in the task list.

{ListID}: The GUID of the list that the workflow associated to the task is running in.

{ItemID}: The ID of the item that the workflow associated to the task is running on.


  • Edit the Nintex My task webpart
  • Go to Item URL Settings and change the Item name URL to Custom and pass the URL you wish to navigate with the Query string


Update a list item when the workflow initiator’s permissions are set to “Read”

Business Requirement

We have a nintex workflow, where in user EDRTest1 will fill the form. So EDRTest1 is the workflow initiator. Once the form is submitted by EDRTest1 we have to set read access to the EDRTest1 and set the contribute permission to user EDRTest2 on that item. Then a task will be assigned to the user EDRTest2 using assign flexi task action. After EDRTest2 approves/rejects the task we have to update an item.


How many of you know update item action would execute under the permissions of the initiator?

The workflow runs as the user who initiated it because this is the way Microsoft designed SharePoint workflow. We cannot change this behavior.

So in this workflow after EDRTest2 task approval, update item action is trying to update the current item with the read access to EDRTest1.

Because of this you will get the access denied problem with the below error.

“The workflow could not update the item, possibly because one or more columns for the item require a different type of information.”

How to solve this issue?

  • Drag on a “Call web service” action instead of update item
  • Configure the url to be your site url/_vti_bin/lists.asmx.
  • Click the padlock icon next to the username field and select the credentials defined above. (Be sure to select a user has contribute access to the item)
  • Press ‘Refresh’ next to the web method drop-down box.
  • Choose “UpdateListItems” from the list of available methods.
  • Click the SOAP Editor button option
  • Paste in the following XML. This particular example updates a field called ‘Status’ to be “Approved”. Note it uses references to define the list name and the ID of the item to update.

 <?xml version=”1.0″ encoding=”utf-8″?>

<soap:Envelope xmlns:xsi=”” xmlns:xsd=”” xmlns:soap=””>


<UpdateListItems xmlns=””>



<Batch OnError=”Continue” ListVersion=”1″>

<Method ID=”1″ Cmd=”Update”>

<Field Name=”ID”>{ItemProperty:ID}</Field>

<Field Name=”Status”>Approved</Field>







Impact of this approach

This approach will change the modified by user value with the user name credential which we are passing to this web service action. But our requirement is to see the last modified by user as EDRTest2.

So what is the work around?

If this is the case the only other option would be to give the user permissions to the item via set permissions action, then a commit pending changes, then the update and then another set permissions action removing the permissions.

Why “Run as workflow owner” is disabled in Action Set?

Business Requirement

Our requirement is to create sub-sites under the site collection based on user request using nintex workflow.  We have attached this nintex workflow in the request form. So whenever an item created to this list, our workflow will run and create a sub-site.

Since the workflow is running with the current logged-in user, it is adding the current logged-in user with full control in site permissions in the site which is created by the workflow. But customer requirement is to remove the current user permission given directly to site. So we wanted to remove the logged-in user from the site once the site is created.

To do this first we have to check the exception in the create site action, if no exception we have to remove the user using RemoveUserFromWeb web method of usergroup.asmx web service.

We wanted to configure this web service action with workflow owner identity so we tried to use Action Set for this. But when we tried to configure the action set the “Run as workflow owner” option was disabled.

This is our development scenario. Please find the screen below


But we solved this by configuring the Service Admin account in Override credentials section of the Create Site action.

Use of Override credentials 

The site will be created using the current security context of the workflow by default.  This can be the rights of the initiator or the rights of the workflow owner.

If an override username and password is provided, the workflow action will use the permissions of the provided account to create the site instead.

Why “Run as workflow owner” is disabled in Action Set? 

This is an expected behaviour of Action Set control. Only actions at the root path of the workflow will have the Run as Workflow Owner option.  If you have an action in any branch, this option will not be available.

Nintex – Delegation Approver Name Problem

What is Task delegation?

The most valued feature of Nintex Workflow is the “Task delegation”. With task delegation, a user can delegate his task to someone else. If the task owner feels that this task is not relevant to me, he/she can delegate the task. When a user is in out of office mode, he/she can setup the task delegation feature as well.

Problem / Bug

Nintex Version: Nintex Workflow 2010 (

We have a nintex workflow with delegation functionality. Initially the task is assigned to user “Radhika Radhakrishnan –CNTR”. Once the task is assigned, this user will get the task notification e-mail. In this e-mail we have configured the nintex provided variable “{Common:ApproverName}” to show the display name of the task owner/approver.

We have configured the nintex provided common variable “{Common:DelegateUrl}” in our task notification e-mail. So that the task owner/approver will click on this link and go the delegation page without opening the task edit form when he/she feels this task is not relevant to me.

Now the user “Radhika Radhakrishnan –CNTR” delegating the task to “Joseph Velliah –CNTR”. At this point of time the same task notification will be sent to the new task owner with the delegator’s comments.

The problem what we faced is; when the task is delegated to “Joseph Velliah –CNTR”, the nintex provided “{Common:ApproverName}” is not changing the display name of the newly assigned task owner. It’s still showing the old approver name in our task notification e-mails.

Please find the screen shot below for the same:



We raised this issue to nintex we got the below response:

“We can confirm that we have replicated this behaviour and it has been raised as a bug. Currently due to the nature of the bug there isn’t a work around to resolve this behaviour in the short term unfortunately”.

“Currently we cannot give a direct time frame to when this issue will be resolved as the bug resolution process can be lengthy and vary dependent on the solution required, code development and testing”.

So Let us hope this bug will be fixed in their next build / version.

Displaying Graphical Workflow Status – OOB


User requirement is to show the progress of a SharePoint Workflow Request in a graphical display to make the end user to understand more easily.


You have followed the following steps to achieve the above mentioned requirement. The request status was created and updated with the help of an InfoPath form, and I have used a 3 level approval Nintex Workflow which will start when an item is created and modified.

The Request Progress Bar is built by the Workflow in the background at run time, one status image which is used at that starting point of the workflow(that is when an item is created), and the remaining Request Progress Bar images are calculated based on the status change.

To map this, I have created four individual images, one for each stage in the process. Example images are included below.

Status 1: Submitted statusbarlevelfirst

Status 4: Completed statusbarlevelfour

These images were uploaded into the Images library and the mapping list was created as shown below: mapping

The Workflow will build the appropriate HTML to show the status bar based on the status change. Nintex Workflow is used to generate this HTML as shown below.

The HTML output generated by the workflow is shown below:

This HTML content is now updated by the workflow on a multiline plant text. But when we view this in SharePoint list view through the browser it will not get interpreted by the browser as an image.

From Christophe’s post I came to know that using CEWP we can convert the plain HTML content into browser understandable HTML content. To do this, you have to add a CEWP at the bottom of the page where you want to show the status and paste the following script into the HTML source editor.

var theTDs = document.getElementsByTagName(“TD”);
var i=0;
var TDContent = ” “;
while (i “) >= 0)) {
theTDs[i].innerHTML = TDContent;
function ExpGroupRenderData(htmlToRender, groupName, isLoaded) {
var tbody=document.getElementById(“tbod”+groupName+”_”);
var wrapDiv=document.createElement(“div”);

var theTBODYTDs = wrapDiv.getElementsByTagName(“TD”); var j=0; var TDContent = ” “;
while (j “) >= 0)) {
theTBODYTDs[j].innerHTML = TDContent;

So, with the help of this script the Request Status Bar now displays the image. Thats it 🙂

final output

Why I am Getting a 401 unauthorized error when using Nintex Query XML on an InfoPath form?


I am trying to read the XML data from an InfoPath form which is located in a form library. I am using the Nintex Query XML action and passing a XML file URL to the form that I want to read. When I run the workflow, I got the following error:

“Error processing XML. The remote server returned an error: (401) Unauthorized.”


This is because we have InfoPath Forms Services in the farm environment, the request for the InfoPath xml file was getting redirected.

Upending  “?NoRedirect=true” at the end of the URL to the XML file as a query string stopped the redirection and allowed me to read the XML data from the InfoPath file.

Check this useful info from msdn – How to: Use Query Parameters to Invoke Browser-Enabled InfoPath Forms?

Nintex – Reusable User Defined Actions

A User Defined Action (UDA) is similar to a custom workflow action; it can take certain input variables and output a result. The actions inside the UDA can be hidden from the end user so they will only see a single workflow action that can actually perform a series of workflow actions or a certain task.

This can be useful when reusing a workflow process across multiple sites or for creating a complex set of workflow actions that end users can easily configure and reuse.

I have created the following Nintex User Defined Actions (UDA) which you can use this in your projects

Add User to Group UDA – AddUserToGroup (

Add User Collection To Group UDA – AddUserCollectionToGroup ( )

Add User Permission to List or Web UDA – AddPermission ( )

Remove User Permission from List UDA – RemovePermission ( )

Remove User from Group UDA – RemoveUserFromGroup (

Get Permission Collection UDA – GetPermissionCollection (

Please find the UDA files here

How to add permissions to a new SharePoint site using Nintex?


  1. I have a Site Request list in the parent site collection.
  2. I have to create a sub-sites with a particular template( such as Wiki) for every site request created in the Site Request List.
  3. Once the sub site is created, I have to set the permission to the new sub-site based on the meta data filled by the requester in the Site Request List.
  4. I have to run a Nintex workflow to create sub-sites,  which will be attached on the Site Request List.

Problem / Issue:

Out of the box with a Nintex action, setting the permissions at the site level is not possible


Instead of expecting a Nintex action for this, you can use the method outlined in this link and the permissions web service method using a Nintex Call Web Service action:

Steps to Implement:

Use Create site action to create a new sub site under the parent site collection as shown below

Use call web service action and call the permissions.asmx web service to add permissions to the Site as shown below



Type: System.String
A string that contains the name of the list or site.
Type: System.String
A string that specifies either List or Web.
Type: System.Xml.XmlNode
An XML fragment in the following format that specifies the permissions to add and that can be passed as a System.Xml.XmlNodeobject:

In the above image, varPermissionXML is an XML input variable which will have the following XML input

<User LoginName=”domain\siteadmin”
Name=”Site Admin”
PermissionMask=”1027801615″ />
<Group GroupName=”WIKI Article Owners” PermissionMask=”-1″ />
<Group GroupName=”WIKI Article Members” PermissionMask=”1011028719″ />
<Group GroupName=”WIKI Article Visitors” PermissionMask=”138612833″ />

If you want the exact PermissionMask number for a specific permission role refer the below xml which I have received from the GetPermissionCollection web method of the same web service.

<GetPermissionCollection xmlns=””>
<Permission MemberID=”2″ Mask=”-1″ MemberIsUser=”True” MemberGlobal=”False” UserLogin=”Domain\siteadmin” />
<Permission MemberID=”3″ Mask=”-1″ MemberIsUser=”False” MemberGlobal=”True” GroupName=”WIKI Article Owners” />
<Permission MemberID=”4″ Mask=”138612833″ MemberIsUser=”False” MemberGlobal=”True” GroupName=”WIKI Article Visitors” />
<Permission MemberID=”5″ Mask=”1011028719″ MemberIsUser=”False” MemberGlobal=”True” GroupName=”WIKI Article Members” />
<Permission MemberID=”7″ Mask=”134287360″ MemberIsUser=”False” MemberGlobal=”True” GroupName=”Style Resource Readers” />
<Permission MemberID=”8″ Mask=”1012866047″ MemberIsUser=”False” MemberGlobal=”True” GroupName=”Designers” />
<Permission MemberID=”9″ Mask=”2129075183″ MemberIsUser=”False” MemberGlobal=”True” GroupName=”Hierarchy Managers” />
<Permission MemberID=”10″ Mask=”1011028991″ MemberIsUser=”False” MemberGlobal=”True” GroupName=”Approvers” />
<Permission MemberID=”11″ Mask=”134418465″ MemberIsUser=”False” MemberGlobal=”True” GroupName=”Restricted Readers” />
<Permission MemberID=”12″ Mask=”134287360″ MemberIsUser=”False” MemberGlobal=”True” GroupName=”Quick Deploy Users” />
<Permission MemberID=”14″ Mask=”138612801″ MemberIsUser=”False” MemberGlobal=”True” GroupName=”Viewers” />
<Permission MemberID=”1073741823″ Mask=”134287360″ MemberIsUser=”True” MemberGlobal=”False” UserLogin=”SHAREPOINT\system” />

That’s it you are done. Hope this will help you 🙂

Reusable – Querying Large Lists using Nintex


We have a SharePoint list with 10,000 items, we have to perform “for each” action on each item one by one and do some processing using Nintex.

Following are our questions:

  • Is there a limit to the number of items that can be collected in the Query List action?
  • Will it handle item counts of 20K, 30k, 50k or more?
  • Also, do we need to be concerned about a time limit for the workflow to complete?  If yes, what is the time limit and can we adjust it for a specific workflow?


We know that there are some limits to querying lists and its internal SharePoint limitations (about List Thresholds).

It’s configurable at the Central Admin -> Manage Web Application -> Resource Threshold

You could do this using Paging in coding but the Query List action doesn’t currently support it.  So you’d have to query the list using a web service call -> Lists.asmx -> GetListItems.

Vadim developed a Nintex UDA and found its working. Kindly download those from the below links.

There are some hard coded values in the workflow, and the UDA expects a constant credential named Farm Admin.

It’s a very useful one, you can use whenever you are querying Large Lists using Nintex.

For more details visit :

Important Note:

I tried with 6000 records ( Id starting from 6001 to 12000) in my SharePoint list. To monitor I am printing the Item Id in the log history action.

In the workflow history I can see all the 6000 item ids printed. But the status of the workflow its showing as “Failed on Start (retrying)” . To avoid this please find the solution in the important note section.

For your information please find the history of the last page below:

10/9/2012 10:18 AM Comment 11984
10/9/2012 10:18 AM Comment 11985
10/9/2012 10:18 AM Comment 11986
10/9/2012 10:18 AM Comment 11987
10/9/2012 10:18 AM Comment 11988
10/9/2012 10:18 AM Comment 11989
10/9/2012 10:18 AM Comment 11990
10/9/2012 10:18 AM Comment 11991
10/9/2012 10:18 AM Comment 11992
10/9/2012 10:18 AM Comment 11993
10/9/2012 10:18 AM Comment 11994
10/9/2012 10:18 AM Comment 11995
10/9/2012 10:18 AM Comment 11996
10/9/2012 10:18 AM Comment 11997
10/9/2012 10:18 AM Comment 11998
10/9/2012 10:18 AM Comment 11999
10/9/2012 10:18 AM Comment 12000

Important Note:

I have seen this issue when trying to start a workflow on many items at once.  SharePoint can’t handle the huge load.  It has an internal limitation of 15 executing actions at a single time.  In most cases, that is fine, because most workflows tend to sit and wait and that is not considered executing.

The other situations I have seen this, is when a single workflow tries to do too much at one time.  It basically hits some type of time-out  So to avoid this put some logic into the workflow, that it does a 1 minute delay after every 100 records or so.  This will solve the problem.