I have a real-time workflow setup to update a field on an entity that does not allow edit from a specific security role. I set this workflow up as an on-demand process and the "Execute as" is set to "The owner of the workflow". The owner is a confirmed System Administrator of the system. Based on this, I would think that even though the user cannot edit the entity directly, it would be able to update the field on the entity using the workflow because the workflow is set to run as the owner.
However, when running the workflow, the user is given a message stating they do not have write permissions on that entity. Shouldn't the workflow run as the elevated owner in this situation or am I misunderstanding what the execute as option does?
I have tried this scenario in both 2015 on prem and online with the same results.
Please help me understand this correctly.
Thanks
*This post is locked for comments