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

Chris over 10 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

0 Chris over 10 years ago

Thanks Racheal, that is a good work-around for unattended nodes. Our issue ufortunately is with Appian expressions running under the initiator context, say on a user input task's input or form expressions. Some of these expressions will fail with something such as a "Work Item Cancelled" error and we cannot get the node to run correctly again, even with reactivating the initator account :(
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 rachealv537 over 10 years ago

csteward- got it. Has anyone from Appian said why when you reactivate a user it does not solve this? Reactivating the user didn't work for us either.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Chris over 10 years ago

I haven't heard from Appian staff on this one unfortunately :(
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 anjannat over 9 years ago

Hi All,
Currently I am facing the same issue, but in my case reactivating the user is working fine without any issue. The solution is simple that once we reactivated the user account just remove him from all the groups which he belongs to and add him back to the same groups and then restart the user input task.

But my concern is how we can resolve this issue without reactivating the user.
Please suggest me if you have any solution for existing processes to avoid this issue.(without reactivating user)

Thank you,
Anji
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel