I had similar exception and fixed it by adding user to Workflow group in SCSM
↧
I had similar exception and fixed it by adding user to Workflow group in SCSM