{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":21369,"path":"integrate-applications/integration-hub/remote-instance-spoke.md","title":"ServiceNow Remote Instance Spoke","bundle":null,"doc_type":null,"release":"australia","body":"\n# ServiceNow Remote Instance Spoke\n\nIntegrate your local and remote ServiceNow instances to export, import, and manage records from your local instance.\n\n## Request apps on the Store\n\nVisit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).\n\n## Integration Hub subscription\n\nThis spoke requires an Integration Hub subscription on the local instance where it will be installed. For more information, see [Legal schedules - IntegrationHub overview](https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/snc-addendum-integrationhub.pdf).\n\n## Spoke version\n\nServiceNow Remote Instance spoke v2.3.2 is the latest version. For version history of the spoke, see [ServiceNow Remote Instance spoke release notes](https://www.servicenow.com/docs/r/store-release-notes/store-integrationhub-rn-sn-remote-instance.html).\n\n## Supported versions\n\nThis spoke was built for the Orlando version and later.\n\n## Spoke dependencies\n\nIf you’re having trouble installing the app, ensure that these dependent plugins are installed:\n\n- ServiceNow IntegrationHub Runtime \\(com.glide.hub.integration.runtime\\)\n- ServiceNow IntegrationHub Action Template - Data Stream \\(com.glide.hub.action\\_type.datastream\\)\n- Complex Object \\(com.glide.cobject\\)\n- ServiceNow Flow Designer - Dynamic Outputs \\(com.glide.hub.dynamic\\_outputs\\)\n- ServiceNow IntegrationHub Action Step - REST \\(com.glide.hub.action\\_step.rest\\)\n- ServiceNow Flow Designer - Dynamic Inputs \\(com.glide.hub.dynamic\\_inputs\\)\n\n**Note:** Some of these plugins are licensable features and require appropriate licenses, if used outside the spoke implementation.\n\n## Spoke requirements\n\nEnsure that the spoke users have only the required minimum permissions to access data in ServiceNow tables. Do not assign elevated privilege roles to users of this spoke unless very much required. This practice ensures controlled access to data.\n\n**Note:** The terms remote instance and local instance are used in these contexts:\n\n- Local instance: This is the ServiceNow instance from which the communication is initiated and established.\n- Remote instance: This is the ServiceNow instance with which the local instance communicates.\n\n## Spoke actions\n\nThe ServiceNow Remote Instance spoke provides actions to export, import, and manage records when events occurs in your local ServiceNow instance. Available actions include:\n\n\n
\n\nCategory\n\n\n\nAction\n\n\n\nDescription\n\n
\n\nChange request Management\n\n\n\nExport Change Request Record\n\n\n\nExports a change request record to a remote instance from the local instance.\n\n
\n\nImport Change Request Record\n\n\n\nImports a record from the Change Request table of the remote instance to the local instance.\n\n
\n\nIncident Management\n\n\n\nExport Incident Record\n\n\n\nExports an Incident record to a remote instance from the local instance.\n\n
\n\nImport Incident Record\n\n\n\nImports a record from Incident table of the remote instance to the local instance.\n\n
\n\nProblem Management\n\n\n\nExport Problem Record\n\n\n\nExports a Problem record to a remote instance from the local instance.\n\n
\n\nImport Problem Record\n\n\n\nImports a record from Problem table of the remote instance to the local instance.\n\n
\n\nTable Management\n\n\n\nLook Up Fields By Remote Table\n\n\n\nRetrieves all the fields from the given remote table.\n\n
\n\nLook Up Local Import Set Tables\n\n\n\nRetrieves information about the given local import set table.\n\n
\n\nLook Up Remote Import Set Tables\n\n\n\nRetrieves information about the given remote import table.\n\n
\n\nLook Up Remote Tables\n\n\n\nRetrieves information about the given remote table.\n\n
\n\nAttachment Management\n\n\n\nCopy Attachment From Remote Instance\n\n\n\nCopies the required attachment from the remote instance.**Note:** You must select the required attachment using data pills only.\n\n
\n\nCopy Attachment To Remote Instance\n\n\n\nCopies the required attachment to the remote instance.**Note:** You must select the required attachment using data pills only.\n\n
\n\nLook Up Local Attachments Names\n\n\n\nRetrieves name of the required attachment.\n\n
\n\nCase Management\n\n\n\nExport Case as Incident\n\n\n\nExports a case record as an incident record to a remote instance from the local instance.\n\n
\n\nExport Case Record\n\n\n\nExports a case record to the remote instance from the local instance.\n\n
\n\nExport Case Task Record\n\n\n\nExports a Case Task record to the remote instance from the local instance.\n\n
\n\nExport Incident as Case\n\n\n\nExports an incident record as a case record to the remote instance from the local instance.\n\n
\n\nImport Case as Incident\n\n\n\nImports a record from the case table of the remote instance as an incident record to the local instance.\n\n
\n\nImport Case Record\n\n\n\nImports a record from the Case table of the remote instance to the local instance.\n\n
\n\nImport Case Task Record\n\n\n\nImports a record from the Task table of the remote instance to the local instance.\n\n
\n\nImport Incident as Case\n\n\n\nImports a record from the Incident table of the remote instance as a case record to the local instance.\n\n
\n\nRecord Management\n\n\n\nCreate or Update Remote Record\n\n\n\nCreates a record or updates an existing record in the remote instance.\n\n
\n\nCreate or Update Remote Record Using Import Set\n\n\n\nCreates a record in the remote import set.\n\n
\n\nCreate Remote Record\n\n\n\nCreates record in remote instance.\n\n
\n\nDelete Remote Record\n\n\n\nDeletes record in remote instance.\n\n
\n\nExport Record Using Import Set\n\n\n\nExports a record from the selected local table to a remote instance.\n\n
\n\nGet Remote Record\n\n\n\nRetrieves the required record information from the remote instance.\n\n
\n\nImport Record Using Import Set\n\n\n\nImports a record from table in the remote instance to the local instance.\n\n
\n\nLook Up Remote Record\n\n\n\nRetrieves the required record from the remote Instance.\n\n
\n\nLook Up Remote Records\n\n\n\nRetrieves multiple records from the remote instance table.\n\n
\n\nUpdate Remote Record\n\n\n\nUpdates the required record in the remote instance.\n\n
**Note:** The **Company** field is required to import or export records using the default transform maps. However, users can modify the transform maps as per their requirement. Also, use the import sets when working with integration involving data transfer.\n\n## Spoke user role\n\nThe ServiceNow Remote Instance spoke provides the Remote Instance Admin \\(sn\\_now\\_remote\\_spk.Remote Instance Admin\\) role that provides administrative rights for all tables that are avaiable with the ServiceNow Remote Instance spoke.\n\n## Spoke transform maps\n\nThe ServiceNow Remote Instance spoke provides sample transform maps in active state and associated sample target tables to demonstrate using transform maps to save the remote ServiceNow instance data in your local ServiceNow tables. You can use these sample transform maps and target tables as reference to create transform maps as per your requirement.\n\nFor more information, see [Transform maps](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/system-import-sets/c_CreatingNewTransformMaps.md).\n\n**Note:**\n\n- By default, the sample transform maps uses **sys\\_id** as the coalesce field. You can customise the transform map script as per your requirement to change the coalesce field.\n- By default, the export and import actions use the spoke tables. You can change this to use different import sets.\n- The time zones may be different in your ServiceNow instances. Ensure that you customise flows accordingly.\n\n## Connection and credential alias requirements\n\nIntegration Hub uses aliases to manage connection and credential information. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you don't need to update any actions that use the connection. For more information, see [Connections and Credentials](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/r-credentials.md).\n\nTwo connection and credential aliases are required for this spoke; one for the local instance and other for the remote instance. For information about setting up the spoke, see [Set up the ServiceNow Remote Instance spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/setup-rem-instance.md).\n\n"}}