How to ebond Service Reqests?

[Suggy]

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)?

[KamilKowalczyk]

The Spoke doesn't support Request integration so I just provided a link to REST API integration. 

As for the Update Sets, Add to Update Set UI Action would do the job.

[ersureshbe]

Hi, I recommend to create the generic catalog item and control 300 catalog items with 1 or 3 generic catalog items.

Define a custom table as a decision table and bring the category, subcategory field. Based on categort, sub category selection auto assignment and approval should be called. This all configuration has been done in the decision table.

Workflows will refer to the decision table and it will do the further activities.