Forum Discussion
Not sure if this will help, but on some of our methods we have a couple of lines that set permissions before doing anything else. If you get this working, I would love to know how.
C# Method
s_Daemon is an Identity that was set up prior to me. It is supposed to be similar to the Aras PLM Identity.
Aras.Server.Security.Identity s_Identity = Aras.Server.Security.Identity.GetByName("s_Daemon");
Boolean PermissionWasSet = Aras.Server.Security.Permissions.GrantIdentity(s_Identity);
I thought about this but I am testing using an admin account and the Workflow Process Path already has Can Add for Administrators, and even World so I am not sure what else is preventing the permissions.
- Nathan_H_4 years agoIdeator I
They will also need Edit permissions to be able to edit an existing item.
- Morgan4 years agoIdeator I
Ah, so likely I would need to take a look at the workflow process item or workflow process activity since these are where the path connects?
- Nathan_H_4 years agoIdeator I
Either give them the permissions in the ItemType (I don't recommend that) or add the line to the method to give them the permission and then remove the permission at the end.
I forgot to add this part from our scripts when I posted before. This removes the permissions.
if (PermissionWasSet==true)
{
Aras.Server.Security.Permissions.RevokeIdentity(s_Identity);
}