I am using Nintex 2010 with SharePoint 2010. I have a question and I hope there is an easy solution without having to modify the workflow.
I have a workflow. In this workflow I have several flexi-tasks. They fall under a state machine. This one flexi-task goes out to 3 approvers at once. The problem is there are people some times who don't respond. So you may have tasks sitting out there for months. There is an approver waiting on these approvals. He wants to be able to at anytime take over and approve/reject any of these tasks without the original approval delegating it to him. At the same time, he doesn't want to receive a bunch of emails. Is there some sort of permission or something he could have to do that? I know I can do it, but I am a site collection admin and I have full rights. He cannot have full rights. Any ideas?
Solved! Go to Solution.
Can you not Manage the Permissions for thoses tasks? I do not know if it is possible in 2010.
I know it is a manual action but if you do not want to change your workflow and it does not happen frequently.
Just an idea,
Agreed. I was wondering if that single change may be a valid resolution if it was a common case. But you make a great point taking it in a different light.
Other options could be to run the NWAdmin command to move all assigned tasks from one user to another user. The site admin could do it on their behalf. You could grant the user higher privileges. You could also use a site workflow with a start form to enter a user to find tasks for and a user to replace assigned tasks to and have the workflow automate the effort in two possible ways, directly changing the assignee field or using the delegation action. I believe if you can change the assignee field, then you should not get any generated emails.
I hope someday Nintex will be as flexible in this regard as OOTB SharePoint 2007 Workflows were, where you could change approvers on the fly through the UI. I think there's already a suggestion about that at uservoice.
I have a similar need and so I switched from a State Machine to a Loop/Switch on an Item Property for the state so that he can move the "state machine" on to the next state by simply change that state property. That said, it doesn't allow him to take over the tasks. I haven't finished it yet so I'm not sure what will happen with the outstanding tasks in my case. I'm assuming I'll need to cancel those tasks if the admin does change the state.
So what permissions would the user need? Usually these managers go on travel and folks are sitting around waiting on items to be approved while some of these people are out of town. And sometimes users' accounts get disabled and things need to get done until all the red tape is finished to get their account back. In my situation, I can't run admin scripts. Only the SharePoint Farm admins can do that.