We have been dealing with many issues based on deactivated user accounts lately.

Chris over 9 years ago

We have been dealing with many issues based on deactivated user accounts lately. With a large company, long process life (required) and many contract employees, this is a frequent scenario. We typically receive errors similar to the one below - bringing the user account back to active status does not resolve the issue and we haven't been able to figure any way around these other than just telling customers to cancel the request and submit a new one - which is not a very good user experience.

"The user [user.name] does not have sufficient privileges to perform the requested action because they are not in any role. (APNX-1-4188-001)"

How is everyone else handling deactivated initiator accounts - since some functionality cannot be coded around (functions/expressions running under pp!initiator context, etc)? More sub processes - put almost all functionality in a sub proecss run under the designer account vs the initiator? Unfortunately after migr...

Discussion posts and replies are publicly visible

Parents

0 mjmallet over 9 years ago

We had that same issue here as well and found a work around. With our Publishing and Translation process (for example) when it is started, we take the name of the pp!initiator and we save it to a process variable (pv!initiator). We use the process variable in the whole process and if we have sub-process, we pass it along, and we made sure to use "Run as whoever designed this process model" in our assignments.. and we deploy using the Administrator account. So if person X started the task and then leaves the company.. the team uses the quick task, assigns a new pv!initiator and all the information is changed. Of course it doesn't change the real initiator.. but at least the process can run along without having to leave person X's account active. :)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 mjmallet over 9 years ago

We had that same issue here as well and found a work around. With our Publishing and Translation process (for example) when it is started, we take the name of the pp!initiator and we save it to a process variable (pv!initiator). We use the process variable in the whole process and if we have sub-process, we pass it along, and we made sure to use "Run as whoever designed this process model" in our assignments.. and we deploy using the Administrator account. So if person X started the task and then leaves the company.. the team uses the quick task, assigns a new pv!initiator and all the information is changed. Of course it doesn't change the real initiator.. but at least the process can run along without having to leave person X's account active. :)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data