While trying to set field value or update list item action after set item permissions for setting workflow initiator’s permission to read only so that he or she could not modify the list item I was getting the following error in email.
The workflow could not update the item, possibly because one or more columns for the item require a different type of information.
On the workflow status page in the history list an event was logged with Error event type and outcome of that event was access denied.
After exploring a little bit I found out that this error was coming because Nintex workflow runs in the user context of initiator so if the initiator doesn’t have permission to modify list items set field value and update list items actions would fail.
There is a way to run the workflow in the context of user who publishes it. Thia option can be enabled by editing an action, go to common settings and then enable “Run as workflow owner”. This option is not available in all actions so to use it in actions where it is not available please drop an action set action in the workflow, enable this setting and then drop the actions you want to use, in my case I was using state machine workflow and then was using set field value.
I hope you find this post useful. Thanks for reading.
After migrating SharePoint 2007 portal to 2010, I noticed that the workflows associated with lists were not available and after researching a bit, I found something interesting on TechNet.
If you had disabled the Workflow Auto Cleanup timer job in your Office SharePoint Server 2007 environment, make sure that you disable this timer job in your new environment also. If this timer job is enabled in the new environment and disabled in the previous version environment, you might lose workflow associations when you upgrade. For more information about this timer job, see Disable preservation of workflow history (SharePoint Server 2010).
I checked the timer job and it was running on both machines so something else was at play here so later I found out here that
“In SharePoint 2010 the 2007 workflows are there to allow any running workflows to complete, but by default creating new instances of the workflows is disabled as the expectations are that you will want to move forward to the SharePoint 2010 workflows.”
And to allow creation of SharePoint 2007 workflows instances, I followed Vinit’s solution which was
- Activate SharePoint 2007 workflows feature in Site Collection Features
Remove ‘none’ from <AssociationCategories>none</AssociationCategories>
Don’t’ forget take backup of these files before modifying them.
I hope you find this post useful, thanks for reading.
I’ve used Nintex in a few projects both for SharePoint 2007 and 2010. My experience has been very good and I usually recommend it to medium sized organizations. Why I think Nintex is good solution, following are top three reasons.
- Creating a workflow is as easy as visualizing one, check out the two-minute overview
- Rich documentation and support, check out Nintex Connect
- Great return on investment, see what their customers are saying.
Today while researching I came across K2underground and found this amazing feature in K2 called K2 SmartActions.
I’m pasting some details from the article which I read (http://www.k2underground.com/blogs/k2/archive/2012/05/09/k2-smartactions.aspx)
K2 SmartActions is a technology that allows for Process participants that receive email Task Notifications to interact with the Workflow Task and the underlying K2 Process via email messages between the user and the K2 Process Server. The goal of this technology is to allow mobile users or user that live within email clients (Outlook, Mail, etc.) the same functionality as users that either interact with K2 Tasks via the K2 Task Worklist or via the associated Task form directly. To accomplish this, we have provided the ability to automatically embed both Task-specific Actions (things like the Approve, Deny, Confer that you’re already building into your Tasks today) along with the standard Redirect, Delegate and Sleep actions that are natively exposed on our K2 Worklist.
K2 SmartActions Configuration Tips