Hi
I am working on version 19.1.
I have a query regarding groups of a deactivate user.
So my requirement is if user selects a group, he wants to know the deactivated uses of that group.
Is here any way of achieving this.
Thanks in advance!!
Discussion posts and replies are publicly visible
Also I have a requirement to deactivate multiple users at the same time. With the smart service "Deactivate User", I can deactivate one user at a time. Kindly give any suggestions for this as well.
Like any Smart Service you can run multiple instances of it using the MNI configuration settings in the 'Other' tab. Note that there is a limit (1000) above which Appian will not run the Smart Service in MNI mode.
Hi,
1. If the user deactivated then the user, then the user no longer a member of that group that the user belongs to. No groups in Appian contains deactivated users.
2. You can run the MNI on Deactivate User smart service to deactivate more than one user at a time.
Once the user is deactivated then they will not part of any groups, By the way how are the users deactivated, is that from Admin Console?
Often we face these type of requirements, So I would prefer every application should contain some way to store the User metadata like the roles he is part of in a DB. I mean here the roles refer to Groups. So Instead of Deactivating directly from Admin Console, better to have an User management application in Appian itself, thus the User management application can do log the activities in a DB and also can extend the application such that any tasks assigned to the user can be assigned back to Group or Supervisor
This is going to require an architecture change. You're going to need to build a mini-app for deactivating users to be utilized in lieu of the Admin console, and really get onto your system admins to use your new Deactivate User App instead of the default mechanism.
As part of the app, you'll want to record all groups that user currently belongs to before deactivating them. That achieved, you'll then want to format the groups to some other data type, such as integers for the group IDs, then persist those in a database table. When that's done, deactivate the user.
This gives you three advantages, even four depending how you build it:
1 You can store the date and time and user that deactivated this user for auditing purposes
2 You can do what you originally asked for and query what groups a user belonged to before they were deactivated
3 You can use the query to manage what former groups a user is put into when they're reactivated
4 You could possibly use this to automate the deactivation process to run automatically on a schedule for Use It or Lose It, etc.
Hi thanigaivelr
Thank you for replying!!
I want to avoid MNI on Deactivate User smart service, any other way of achieving this.
Will work as per your suggestion.