- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2023 11:43 AM
So far I have identified two:
Table name | Description |
change_request | Change request main table ? |
change_task | Tasks linked to a change request (1:*) ? |
What other ones are there that are important to know? If you could also supply a description that would be fantastic!
Thanks in advance
Solved! Go to Solution.
- Labels:
-
Change Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2023 12:34 PM
That's kind of a broad question. Change is a whole application menu by itself with links to several tables. The form for a change request also has several related lists at the bottom. It depends on what is being used and by who.
Really, the "main" table is change_request. The related lists at the bottom of the form would likely be considered secondary with some being "more important" than others depending on who is looking at the record. Their tab labels are self-explanatory for their purpose as well. Below is what is in my OOB Tokyo PDI:
- task_ci - Affected CIs where the task is the CHG
- task_cmdb_ci_service - Impacted Services/CIs where the task is the CHG
- sysapproval_approver - Approvers who need to approve the CHG
- change_task - Change Tasks where change request is the CHG
- problem - Problems where change request is the CHG
- incident -
- Incidents Fixed By Change where change request is the CHG
- Incidents Caused By Change where caused by change is the CHG
- task_sla - Task SLAs where the task is the CHG
- task_outage - Outages where the task is the CHG
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2023 12:34 PM
That's kind of a broad question. Change is a whole application menu by itself with links to several tables. The form for a change request also has several related lists at the bottom. It depends on what is being used and by who.
Really, the "main" table is change_request. The related lists at the bottom of the form would likely be considered secondary with some being "more important" than others depending on who is looking at the record. Their tab labels are self-explanatory for their purpose as well. Below is what is in my OOB Tokyo PDI:
- task_ci - Affected CIs where the task is the CHG
- task_cmdb_ci_service - Impacted Services/CIs where the task is the CHG
- sysapproval_approver - Approvers who need to approve the CHG
- change_task - Change Tasks where change request is the CHG
- problem - Problems where change request is the CHG
- incident -
- Incidents Fixed By Change where change request is the CHG
- Incidents Caused By Change where caused by change is the CHG
- task_sla - Task SLAs where the task is the CHG
- task_outage - Outages where the task is the CHG
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2023 01:29 AM
Thank you. Yes, it is a broad question, but I am gathering this information from an external reporting perspective. I came across the following article for Asset and found it very useful, and was hoping for something similar for change_request. I think the information you have provided has managed that 🙂
Asset Management — ServiceNow Elite
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2024 06:32 AM
Hi, were you able to find something similar like Asset Management for Change? The dashboard in the link looks great, and I’m curious if there’s a pre-built version available for Change as well.