- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2022 04:38 AM
From the incident with help of Hamburg when we create Standard Change, Configuration item and Services are not getting copied into the Change request created. It is creating Change with blank values for those two fields. Does anyone have any idea how to achieve this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2022 07:23 AM
The situation would depend on which change is appropriate, based on the organization's definitions of each change. Standard Changes should use Std Change templates where the CI should already be defined, per the template for simple, repeatable changes. If not standard, than a normal change should be used, and as you'll see, the CI field does get populated as a result of that:
You would just need to update this UI action to add a line for the Service field as well. Same goes for emergency change (if that's appropriate for expedited resolution/recovery based on the incident.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2022 05:55 AM
With the way Standard Changes are meant to work OOB, and in accordance to the ITIL framework, data like the service and CI should be defined in the Standard Change template, and auto-applied when you select the pre-approved standard change template to instantiate. Standard changes are meant to be repeatable (and having already been repeated numerous times) changes, and as such, require validation that it has been repeated successfully numerous times against a particular CI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2022 05:58 AM
So which Change request will be best suitable for such scenarios?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2022 07:23 AM
The situation would depend on which change is appropriate, based on the organization's definitions of each change. Standard Changes should use Std Change templates where the CI should already be defined, per the template for simple, repeatable changes. If not standard, than a normal change should be used, and as you'll see, the CI field does get populated as a result of that:
You would just need to update this UI action to add a line for the Service field as well. Same goes for emergency change (if that's appropriate for expedited resolution/recovery based on the incident.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2022 07:24 AM
You can use Normal Change Request for this and in that Context Menu UI Action you can add code to auto populate those fields from Incident to Change if that is not happening.
Thanks
Anubhav Ritolia
ServiceNow Rising Star 2023