Hi, I recently added permission groups to a workflow, and ever since, users have been receiving the following error message:
The workflow could not update the item, possibly because one or more columns for the item require a different type of information : Access Denied
All I understand at this point is that it is a permissions error, and it must be something to do with the level of permissions that the initiator has because this error doesn't occur for me whenever I initiate an item. (I included myself in all of the 'Set item permission' actions.)
The 'MCR Workflow Error' attachment shows a snippet of the workflow where the error occurs...
Here is some more information on the permissions that I have set-up:
I hope someone can help to resolve this issue
Solved! Go to Solution.
as long as your initiator is a member of the group Asset Maintenance Function - Offshore the update should be possible.
If you try to update the item manually using the credentials of the workflow's initiator in your scenario, does the update perform as expected? Otherwise you could try to add a test user to the group mentioned and try the update with that user instead.
I've never used the Commit Pending Changes action before... Where would be a good place to put this?
I used to use the multiple update item action but I'd forget what was in there so found it easier to separate them all. Can this cause problems?
In this scenario the initiator is a member of the group, and the error is still occurring. In another scenario, I had someone initiate a form who wasn't in that particular group and they couldn't get passed the previous branch.
I've never had this issue before with previous workflows so I'm a little confused why it's happening.
It's all about this concept:
This is taken from Caroline Jung's InspireX 2017 presentation on permissions in Nintex (it's an excellent read if you get a chance the whole presentation can be found here: https://vimeo.com/207548019 and https://www.nintex.com/-/media/files/resources/events/inspirex-2017/managing-permissions-when-a-work...)
So I would say add a commit pending changes after a set field and before a set item permissions. See if that helps any?
I wouldn't say your approach will cause problems but update item would slimline it - it's whatever you are most comfortable with at the end of the day.