Any Best Practice Around Retiring Assignment Groups in ServiceNow?

[nathaniecheung]

Are there any best practices in retiring an assignment group in ServiceNow?

I want to be able to automate the process around deactivating groups; however, I want to determine what business rules, catalog items, email notifications, script includes, etc. are related to the assignment group before retiring. 

[Harshinya1]

I have implemented this and i followed below steps

1. Retire the assignment group in the source, Ex: AD or if ServiceNow is the source that is easier to handle

2. Create a catalog item for the owners, to deactivate groups when they think they are ready. Best practice would be removing all roles and migrating all the members to another group

3. Catalog item should contain a forwarding group to forward any incidents, knowledge, approvals or tasks assigned to the group that is being requested to be retired. If not all the tasks and approvals will be orphaned

4. Attach a workflow and migrate any incidents, knowledge, approvals or tasks assigned to the group that is being requested to be retired to the new group

5. Deactivate Group once migration to new group is completed

Hope this helps

[nathaniecheung]

Hi Harshinya,

Thank you for your response! That's a good point you make where it's important to create a forwarding group in order to avoid orphan approvals and tasks.

To get into the finer details, how would I go about creating a script to check which workflows, business rules, scripts, etc. contain a certain assignment group before I create the forwarding group? It's a similar concept that we have in Test Cross Scope (in Studio, where you can check where the code lives). 

Thank you in advance!

Nathanie