'Copy change' not available for Standard Changes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-29-2017 05:17 AM
Hi All,
I have observed that Standard Changes do not have Copy Change button/ feature in Helsinki version.
For Normal and Emergency Change, Copy change is available and works as expected.
Can anyone please tell me why ServiceNow have not provided Copy change feature for Standard Changes.
And if we want to do that, what is the best approach to do that.
- Labels:
-
Change Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-29-2017 05:25 AM
Hi Neetika,
I don't know why, but it I found out where... It all comes down to the ChangeUtilsSNC script include and a method called isCopyRulesValid(). This would be a good question for support. There's got to be a reason and I'm curious to find out what is so special about standard change requests.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-29-2017 07:40 AM
Hi Chuck,
Thanks for your reply...
Script include 'ChangeUtilsSNC' is protected read only.
How can I override this to make Copy Change Work for STandard Changes

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-29-2017 07:47 AM
In theory, you can extend the class and write your own, but I suspect ChangeUtils (not protected) is hard coded to call ChangeUtilsSNC. You may have to modify both.
Do this with caution since once you modify these scripts, you will no longer receive updates.
It would be advisable to call support to see if there is another way to do this without modifying OOB records. There may be a system property that I'm not aware of to configure this rather than customize it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-26-2018 12:32 AM
Per ITIL:
Standard changes (pre-authorised) A standard change is a change to a service or infrastructure for which the approach is pre-authorised by change management that has an accepted and established procedure to provide a specific change requirement. The elements of a standard change are:
- There is a defined trigger to initiate the request for change
- The activities/tasks are well known, documented and proven
- Authority is given in advance (these changes are pre-authorised)
- The risk is usually low
In real-world terms, standard changes are frequently service catalog offerings and are tied to a template or some type of automation.
Per the first item in the list, you use the defined trigger to initiate the standard change; you do not copy an existing standard change.
You would only use an existing change to create a new standard change template if it does not yet exist as a standard change.
Ed Wajs
ServiceNow Technical Support