- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2019 03:21 PM
Hello,
I was asked to remove some groups.
I think it would be better to disable the groups than completely delete it. But I am wondering if I do so some workflow associated to these groups, or some opened ticked will be affected and caused some mess in the system.
It would be possible as well that the names of these groups are hard-coded somewhere. So how to check that ?
Do you have some suggestions or recommendations which should draw my attention ?
MR
Solved! Go to Solution.
- Labels:
-
Best Practices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2019 03:27 PM
Ravel,
As Allen stated is never a good idea. However sometimes necessary. I use a global search tool on share to search for hardcoded sysid's of groups.
It will also search inside of workflows which is a lifesaver in this case.
Give it a try.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2019 03:25 PM
Hi,
Best practice is to never delete anything, but "retire" it. So you can run a report for tasks assigned to that group to ensure there isn't any orphaned tasks...check any assignment rule routing, etc...but ideally you'd just uncheck the active box and retire it that way. Also consider removing roles and members.
We don't know what all you have set up for groups, but usually it's pretty rare to have to retire a group, should go through Change and see if there's any discrepancies there.
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2019 03:47 PM
Hi Allen,
Thanks for your quick reply. I 'll try it.
FYI, the group should be retired as the scope of the project has been changed.
I have just one question for my understnding, why I need to remove also members and roles as the group is already retired so cannot be anymore assigned ?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2019 04:29 PM
Technically, you don't have to...but the group is retired so for role allocation and membership it would be wise to also retire those and clear those out. If the group is every reactivated, you could have it reactivated with inaccurate information, being the roles or the members. Really no reason to keep any of that intact?
I guess that's up to you. Hence why I said consider...not...mentioned in the same line about "best practice". More of an OCD thing? Perhaps? lol.
Anyways.
There ya go!
Please mark any post/reply as Helpful, if it was and the Correct answer as Correct. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2019 03:27 PM
Ravel,
As Allen stated is never a good idea. However sometimes necessary. I use a global search tool on share to search for hardcoded sysid's of groups.
It will also search inside of workflows which is a lifesaver in this case.
Give it a try.