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
Did you Save and Publish or just Save? You must publish for it to change the process designer. FWIW I also strongly recommend that you always save and publish because it creates a new major version each time and is easier to troubleshoot / rollback as necessary.
i had saved and published it. I thought my name will pop up but still his name is only coming. Really not sure what I am missing
For Dev designer users, the approach I've found best is to change their username slightly and add them to the "Service Accounts" group. This prevents them from logging in, and prevents them from auto-expiring (hence any impacts on running instances). Once you're sure there are no more running instances under that account's authority, you can deactivate them more permanently.
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)?
Phil Barton said: an error is returned and can only be resolved be reactivating
This gonna go back and forth after completion again you need to deactivate.
I don't know how helpful my suggestion would be but, Upon deactivating User update the record entry values with some service account (If you don't need to know about particular user) .
Therein lies the problem with the deactivate user functionality. From an audit perspective we need to retain who made which entries and when. Overtyping 000s/ 0000s of row entries is not a valid option to maintain data integrity. Deactivation only works for non-participative/read-only users who have left the business. I'm sure that this is not a unique position for any company using Appian to come across.