Integration Hub Remote Process Sync

  • Release version: Yokohama
  • Updated January 30, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Integration Hub Remote Process Sync

    Integration Hub Remote Process Sync enables ServiceNow customers to create one-way or bidirectional integrations across multiple ServiceNow instances, ensuring that business process flows remain synchronized. This capability is designed for complex multi-instance integrations and requires an Integration Hub subscription. It replaces the older eBonding spoke and offers advanced automation for cross-instance workflows using Workflow Studio subflows.

    Show full answer Show less

    Key Features

    • Cross-Instance Process Automation: Automate business processes that span various ServiceNow instances, keeping stakeholders updated in real time.
    • Data Synchronization and Correlation: Manage synchronization of records, attachments, and journal fields across instances with a robust correlation engine and queueing system to ensure ordered delivery of data updates.
    • Error Handling and Troubleshooting: Utilize the built-in execution engine within Workflow Studio to manage errors and outages in multi-instance automated processes.
    • Support for Domain Separation: Synchronize process flows across domain-separated instances while respecting domain boundaries for configuration tables, queue tables, and execution contexts.
    • Role-Based Access Control: Predefined roles enable precise management of permissions, including creating and managing sync definitions, accessing APIs, and running inbound and outbound flows with appropriate table access.

    Key Outcomes

    • Seamless integration and synchronization of business processes across multiple ServiceNow instances, enhancing operational consistency.
    • Improved automation reliability with ordered delivery and error management, reducing manual intervention.
    • Effective management of multi-tenant environments through domain separation support, maintaining data integrity and security.
    • Streamlined development and maintenance of integrations via Workflow Studio subflows and role management, facilitating scalable process automation.

    Getting Started

    Before implementing Remote Process Sync, evaluate your integration needs against other multi-instance integration options like Instance Data Replication and the Remote Instance spoke. Remote Process Sync is best suited for complex, high-level business process integrations. When ready, follow ServiceNow's guidance on building and managing Remote Process Sync integrations to leverage its full capabilities.

    Integration Hub Remote Process Sync enables you to set up one-way or bidirectional integrations among multiple ServiceNow instances, so that your process flows stay in sync.

    Note:
    Integration Hub Remote Process Sync requires an Integration Hub subscription. For more information, see Legal schedules - Integration Hub overview.

    An Integration Hub Remote Process Sync integration lets you span automated workflows for your business process across multiple ServiceNow instances. As a service provider, keep multiple customer instances in sync automatically, using Workflow Studio subflows to automate your process's workflows for all of your customers.

    Keep process flows across multiple instances in sync. For example, automate software request fulfilment among customer and vendor instances.

    Benefits

    Integration Hub Process Sync provides you with these benefits:
    • Automate cross-enterprise automated processes that span multiple instances, keeping various process stakeholders up-to-date
    • Manage how to synchronize and correlate your record, attachment, and journal field data across multiple instances
    • Ensure order delivery for data updates in remote instances, using a standalone correlation engine and queueing system
    • Manage and troubleshoot errors and outages in your automated mutli-instance processes with the built-in execution engine in Workflow Studio.

    Roles

    By default, Remote Process Sync provides the following roles that you can assign to users:
    Role Users with this role can
    ih_process_sync Create, update, or delete process sync definitions and related records.
    ih_process_sync_api Access Remote Process Sync APIs only.
    ih_process_sync_run_as Run outbound and inbound flows associated with a process sync definition. This user must have access to the tables for which any records are created or updated in the flow.

    Domain separation

    You can use Remote Process Sync to synchronize process flows among multiple domain-separated instances. In a domain-separated environment, the following conditions apply:
    1. When building your integration
      • Configuration tables have a sys_domain, and data is domain separated.
      • Configuration tables are meant to be in the same domain as the parent configuration record.
      • Subflows may be chosen from the current or any parent domain.
      • No tables have sys_overrides , and thus cannot override business rules or UI actions from parent domains.
    2. When your integration runs
      • Only records from the configuration domain and associated child domains are captured.
      • Queue tables have a sys_domain. The outbound record is stored in the same domain as the captured source record. The inbound record is stored in the same domain as the Inbound API user in the Remote System record.
      • The outbound subflow runs in the same domain as the queued record.
      • The inbound subflow runs in the same domain as the user specified in the Remote System record's Run Inbound Flows as field.

    Getting started

    Before deciding to move forward with Remote Process Sync as your integration framework, consider how this framework compares to other multi-instance ServiceNow AI Platform® integrations. While solutions such as Instance Data Replication and the Remote Instance spoke support simple multi-instance integrations, Remote Process Sync supports more complex multi-instance integration use cases, focusing on integrating instances by high-level business processes.
    Note:
    Remote Process Sync replaces the eBonding spoke for integrating instances.
    Figure 1. Comparison of Instance Data Replication, Remote Instance spoke, and Remote Process Sync
    Instance Data Replication and the Remote Instance spoke support simple integrations for an entire table or using ServiceNow AI Platform APIs. Remote Process Sync supports more complex multi-instance integrations.

    When you're ready to start building and managing a Remote Process Sync integration, learn the basics of Getting started with Remote Process Sync.