Need to find what demo data got enabled when we have installed sn_grc plugin in servicenow and GRC

[Sreedhar3]

Hi Team,

Greetings for the Day!!!

We have encountered an issue, while installing GRC related data we have loaded the Demo data also and it is causing an issue. Is there any way where we can find what demo data we got it into our instance and how can we get rid of those data. We are following the steps like policies, Policies to entities etc.,

Any help would be appreciated 
@Adelina

Best regards

Sreedhar

[Aravind2799]

Here's how you can identify and remove demo data related to GRC in your ServiceNow instance:

Identifying Demo Data:

1. Keywords and Prefixes: Look for keywords or prefixes commonly used for demo data in field values. These might include "Demo", "Sample", "Test", or specific prefixes like "GRC-DEMO-".
2. Sys IDs and Ranges: Demo data often has reserved sys_id ranges. Check your system documentation or search online for known GRC demo data sys_id ranges.
3. Inactive Users and Groups: Demo data may include inactive users and groups easily identifiable by their status.

Locating Demo Data:

1. GRC Tables: Focus on GRC-related tables like policies, entities, assessments, controls, etc. These are likely targets for demo data.
2. System Logs: Review system logs around the time the GRC data was loaded. Look for messages mentioning "Demo Data Load" or similar. These logs might indicate which tables were populated.
3. Use GlideRecord Queries: You can write GlideRecord queries to search for specific keywords or sys_id ranges in relevant tables. For example:

var gr = new GlideRecord('grc_policy');
gr.addQuery('name', 'CONTAINS', 'Demo');
gr.query();

while (gr.next()) {
  // You can identify demo records here (e.g., log sys_id)
  gs.info('Possible Demo Policy: ' + gr.sys_id + ' - ' + gr.name);
}

Removing Demo Data:

1. Manual Deletion: If the amount of demo data is small, you can manually delete the identified records using the user interface.
2. Delete Script (Caution Advised): For larger datasets, consider writing a script using GlideRecord to delete records matching your demo data criteria. However, proceed with caution and have a good backup before running such a script. Ensure you have accurate criteria to avoid deleting non-demo data accidentally.
3. System Import Sets (Recommended): If your ServiceNow instance supports System Import Sets, you can explore creating an import set that excludes demo data based on your identified criteria. This allows for a more controlled deletion process.

Advice :

• Involve your system administrator for guidance on identifying and removing demo data, especially when using scripts.
• Consider the impact on dependent records before deleting demo data. For instance, deleting a demo policy might also impact demo assessments linked to that policy.
• If unsure about the origin of specific data, err on the side of caution and don't delete it.

Thanks

Aravind Panchanathan