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

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...

OriginalPostID-137169

OriginalPostID-137169

  Discussion posts and replies are publicly visible

Parents
  • Well we have not had time to upgrade all older process models yet, so while we're heading toward this method in new process model design, we will have potentially hundreds of thousands of requests initiated in the older process models before we can afford time to re-work those.. Then whenever an initiator leaves the company, we run into these issues..
Reply
  • Well we have not had time to upgrade all older process models yet, so while we're heading toward this method in new process model design, we will have potentially hundreds of thousands of requests initiated in the older process models before we can afford time to re-work those.. Then whenever an initiator leaves the company, we run into these issues..
Children
No Data