How to ebond Service Reqests?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2023 11:23 PM
Hello,
Our customer is using ServiceNow and they have around 300 Catalog items. Now due to some business reasons, a subset of users cannot have direct access to this instance. Hence they have bought another instance and they are expecting to have all those 300 catalog items in that NEW instance.
So once the new instance is loaded with all those 300 items, users will start using it to create SR's and that should get ebonded to the original instance so that it can be fulfilled. and overall the SR's should be ebonded (bi-directional sync)
Question - Whats the easiest way to replicate the existing catalog items to the new instance (Clone is not an option)?
- Labels:
-
Architect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2023 12:16 AM
Hi,
I would consider Update Sets.
As for SN to SN integration check this thread:
Hope that helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2023 07:14 AM
Hi @KamilKowalczyk Thanks for replying. Update set is not an option because all those catalog items were created long back and its not maintained/documented.
The 2nd link that you shared does not talk about ebonding Service Requests.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2023 07:29 AM
Hi, @Suggy
You can create a new Update Set and push whatever you need, including Cat Items and referenced items.
As for the link. I provided an example of how you could connect SN to SN. The example is based on the incident table. As for SRQ - different table but the approach would be the same or similar.
Good Luck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2023 07:31 AM
That sounds like a lot of work. I don't believe ebonding spoke currently support service Request integration.
I think the approach should be
1. Recreate service Catalog forms in new instance. (You will can refer this -https://www.servicenow.com/community/now-platform-forum/how-to-capture-complete-catalog-item-in-upda...)
2. Then build flow/workflow using catalog APIs to create a service request in Old instance when a request is created in new instance.
Might also need to build scripted REST APIs in the Old instance if you want to store the correlation id in both instance.
3. Table synching in sc_request,sc_req_item,sc_cat_task can be created to synch the data from old Instance to New instance (if you have already established the correlation)
