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.
Thanks stefan. Will it have any impacts on the objects which are saved by them?
Not at all.
Thank you so much stefan
If not covered under an enterprise license, will you be charged for the active user?
Discuss this with your Appian account exec, but in my experience the counting of active users is pretty flexible.
In my scenario, basic users that contribute and leave an audit trail entry in our tables cannot be deactivated without a subsequent error message. To mitigate these users from being able to be chosen for tasks ever again we can only mark them as "DO NOT SELECT" in their surname. This is crude, effective, but an ugly user experience (especially as they still appear in group dropdowns. Are there any best practices for 'hiding' these users, whilst maintaining a record of their contributions?
Maintaining groups or a table specific to users available for the selection and not (Moving them to a group being a container).
Tasks or call-ups refer back to a basic user within a record entry. If a user is then deactivated (i.e. leaves the company), an error is returned and can only be resolved be reactivating. Given that the 'deactivate user' functionality is present in Prod. does guidance/best practice exist (specifically to avoid errors)?