How can I copy my changes to a catalog item to another ServiceNow instance?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2022 09:25 AM
We have a prod, test, and dev environment in our system. We would like to allow small changes to be made in prod and create a way for those changes to copy down to the other 'lower' environments. We'd need the sysID to match the versions that are modified in the other environments. I've looked into using an API but have been facing issues with some fields not updating. Thanks for the help.
Matt

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2022 02:28 PM
Hi,
Making changes directly in production, having APIs and then make stuff migrate from Production to Dev is not the right way to do it and should be avoided.
Best approach or instance strategy is to have update sets or application repository to migrate changes across instance from Dev to Test|UAT|Prod. For having the production synced with non-prod instances it's good to have a cloned scheduled over the course of 2/3 months.
.
BR.
Ishaan Shoor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2024 06:30 PM
Catalog builder is the way to go.
Many organisations allow 'super' users in prod access to catalog builder. Using it they can make small changes to existing catalog items, or create new items for publishing.
You build a templates which will enforce some uniformity, then staff can use the templates and build what they need.
You can of-course have an approval process if required, similar to the process used in the KB article approval process, or empower teams to have their own process and publish items immediately.
When catalog builder is used to make changes to catalog items, it creates an update set containing the work. Once the item is live you simply apply the update set to the lower environments.