Welcome to Community Week 2025! Join us to learn, connect, and be recognized as we celebrate the spirit of Community and the power of AI. Get the details  

Remote Instance Spoke best practices

kim-lindgren
Kilo Sage

My team has a requirement to set up Remote Instance Spoke to automate the creation of some records from the prod instance down to test and dev. Aside from the documentation, we haven't seen any real examples of how to work with this in practice.

 

First, we were unsure whether records should be created in both test and dev directly from prod, or if we should setup a "cascade" record creation where a flow in prod creates a remote record in test and another flow in test creates the record in dev. We prefer the first solution because we don't want to keep track of a lot of different flows doing different things in prod and in test, but this is just our own conclusion.

 

But ServiceNow seems to only allow one target instance per connection, which makes it seem as if the "cascade" solution is preferred? We did find a community thread about connection child aliases, but we don't fully understand it. We tried by setting the dev instance connection in the child alias to the test instance connection (the "default connection"), thinking that this would then create a Remote Instance Record in dev as well, but it still only created the remote record in test.

 

We also wonder if we should have different "default connections" for different instances, or if we should have the same default connection in both prod and in test.

 

Best regards,

Kim

0 REPLIES 0