Assignment group Deactivation

Manikanta Kota
Mega Guru

‎09-30-2024 12:06 AM

Hi Everyone,

 

I want to deactivate the existing assignment Groups using from past 6 years whicjh tables we need to cross verify before deactivate that group except Itil (incident , problem , change, knowledge, catalog).

Regards,

Manikanta. Kota

  • 1,367 Views
5 REPLIES 5

VishaalRanS
Tera Guru

‎09-30-2024 12:18 AM

Hi @Manikanta Kota 

 

Please go through the following link below:

Solved: Best practices for disabling an Assignment Group -... - ServiceNow Community

 

Thanks, and Regards

Vishaal

Please mark this response as correct or helpful if it assisted you with your question.

Mark Manders
Mega Patron

‎09-30-2024 12:31 AM

You will need to verify all tables that have a reference to the 'sys_user_group' table to ensure that they all have 'active is true' in the reference qualifier, because otherwise you can still select them on records you no longer want to select them.

Also: check any automation (assignment rules, business rules, client scripts, work(flows), etc) used for setting the assignment groups. If they are set in there, you can inactivate all you want, but they will still get used for assigning.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

Sai Krishna6147
Mega Guru

‎09-30-2024 01:00 AM

Hi @Manikanta Kota 

To deactivate assignment groups that have been inactive for six years, you'll need to cross-verify several tables beyond the ITIL tables (incident, problem, change, knowledge, catalog) to ensure that deactivating the group won't disrupt any ongoing processes or data integrity.

Here are the additional tables to consider:

1. Task Table (task):

  • Check if there are any active tasks assigned to the group.
  • Ensure that deactivating the group won't leave tasks unassigned.

2. Incident Table (incident):

  • Verify if there are any open incidents assigned to the group that require further action.
  • If there are, consider reassigning them to a different group before deactivation.

3. Problem Table (problem):

  • Check if the group is associated with any active problems.
  • If so, ensure that the problem is resolved or assigned to a different group before deactivation.

4. Change Table (change):

  • Verify if the group is involved in any ongoing change processes.
  • If so, complete or reassign the change before deactivating the group.

5. Knowledge Table (kb_knowledge):

  • Check if the group is associated with any knowledge articles.
  • If so, consider transferring ownership of the articles to a different group or updating the associated groups accordingly.

6. Catalog Item Table (catalog_item):

  • Verify if the group is assigned to any catalog items.
  • If so, reassign the catalog items to a different group before deactivation.

7. User Table (sys_user):

  • Check if any users are directly assigned to the group.
  • If so, reassign them to a different group or remove their group assignment before deactivation.

8. Group Table (sys_group):

  • Verify if the group is a member of any other groups.
  • If so, remove it from those groups before deactivation.

9. Configuration Item (CI) Tables:

  • Check if the group is assigned to any CIs.
  • If so, reassign the CIs to a different group or remove the group association before deactivation.

Refer : Solved: Best practices for disabling an Assignment Group -... - ServiceNow Community