Hi - since an user account can only be deactivated but not removing it we are fa

We are doing as Abhi mentions above, we run deacivations though a custom process that renames the account with something like 'XXX' at the end, then deactivates - which frees up the username to be used later. This seems like the best solution thus far, until Appian gives us the ability to define the unique ID for the record (user ID would be great). This would also solve the situation of users changing names (married, incorrectly fed from AD initially, AD migrations, etc) which currently causes previous task history and permissions to be lost.

We are doing as Abhi mentions above, we run deacivations though a custom process that renames the account with something like 'XXX' at the end, then deactivates - which frees up the username to be used later. This seems like the best solution thus far, until Appian gives us the ability to define the unique ID for the record (user ID would be great). This would also solve the situation of users changing names (married, incorrectly fed from AD initially, AD migrations, etc) which currently causes previous task history and permissions to be lost.