We have been experiencing some difficulties using certain tasks within Nintex workflow. We have set up a number of workflows using the Flexi Task all of which have not been successful.
The Flexi Tasks sends the notification email to the user informing them there is an item which they need to respond to. The user responds, but the workflow doesn’t pick up or store the response, however it does pick up their comments and acknowledge the fact that the item has been updated in the workflow tasks list. The workflow hangs at the Flexi Task showing a status of ‘pending’ and continues waiting for the user to respond. If the user then tries to respond again the following error is displayed:
This task is currently locked
by a running workflow and cannot be edited. at
Microsoft.SharePoint.SPListItem.PrepareItemForUpdate(Guid newGuidOnAdd, SPWeb
web, Boolean bMigration, Boolean& bAdd, Boolean& bPublish, Object&
objAttachmentNames, Object& objAttachmentContents, Int32&
parentFolderId)
at Microsoft.SharePoint.SPListItem.UpdateInternal(Boolean
bSystem, Boolean bPreserveItemVersion, Guid newGuidOnAdd, Boolean bMigration,
Boolean bPublish, Boolean bNoVersion, Boolean bCheckOut, Boolean bCheckin,
Boolean suppressAfterEvents)
at Microsoft.SharePoint.SPListItem.Update()
at
Nintex.Workflow.ApplicationPages.ApproveReject.btnRespond_Click(Object sender,
EventArgs e)
at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String
eventArgument)
at
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl,
String eventArgument)
at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
We are experiencing the same issue with Request Data and Request Approval.
In event viewer we also receive this which I’m not convinced isn’t a red herring:
Workflow Soap: GetWorkflowDataForItem failed Item: http://................................./Workflow%20Test/Forms/Document/template.dotx Value does not fall within the expected range.
It seems that the outcome is not being stored in the work flow task so therefore cannot carry on with the workflow as it cannot detect a response. We’ve used the help files to check that the tasks have been configured correctly. Can anyone please offer any insight to why we may be experiencing these problems?
We have also tried creating a new task list and pointing the work flow to use that one but no luck. There simply doesn't seem to be a field on the task to store the outcome value.
(NW2007 11301)