What will happen to the objects that are last modified by a user whose account is going to be deactivated soon?What are the precautionary steps that need to be taken while deactivating a user in appian? What about process models which are configured to run as whoever designed the process model??
Discussion posts and replies are publicly visible
In general, I do not recommend to deactivate users. The reason is that ANY process that runs in that user context will fail. This includes active instances started by that user, but also the configurations you mentioned.
Why do you want to deactivate users?
Hi Stefan,
Lets assume if the user is leaving the organization we generally deactivate the user to remove the tool access.
So what steps can we take to handle this kind of scenario?
Thanks in Advance
All my clients use some type of single sign on. Once the user is removed there, he/she has no access to Appian anymore.
Which environment are you working on in this case? There are two scenarios I can think of:
I am thinking about development environment. What about the objects that are saved by the person whose user account is going to be deactivated? Will it cause any problem in future??
Thanks stefan. Will it have any impacts on the objects which are saved by them?
The only objects that matter are process models, and the only reason those matter is if they are configured to run as whoever designed the process model. Typically anyone working on those processes will republish them anyway once they make changes, so it isn't usually much of a problem.
Not at all.
Thank you so much stefan
I have one process model which i have saved recently and its configured to run as whoever designed the process model. When it gets executed, it is showing started by as the previous designer name in monitoring mode and not my name. We both are system admins for the environment. Any comments on this behaviour Peter??