Integration Hub Remote Process Sync
Summarize
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 workflows remain synchronized. This capability is ideal for service providers managing multiple customer instances, allowing automated workflows to be coordinated seamlessly using Workflow Studio subflows.
Show less
Note that this functionality requires an Integration Hub subscription.
Key Features
- Cross-instance process automation: Automate business processes that span multiple ServiceNow instances, keeping all stakeholders updated.
- Data synchronization and correlation: Manage synchronization of records, attachments, and journal fields across instances with a dedicated correlation engine and queueing system to ensure ordered delivery of updates.
- Error management and troubleshooting: Utilize the built-in execution engine in Workflow Studio to handle errors and outages in multi-instance automated processes.
- Support for domain separation: Synchronize process flows across domain-separated instances with domain-aware handling of configuration, queue, and inbound/outbound records.
- Role-based access control: Assign roles like process sync definition management, API access, and flow execution to control user permissions effectively.
Practical Benefits for ServiceNow Customers
- Maintain synchronized automated workflows across multiple ServiceNow environments, enhancing consistency and operational efficiency.
- Reduce manual coordination efforts by automating updates and data sharing between instances.
- Support complex multi-instance integration scenarios that go beyond simpler solutions like Instance Data Replication or Remote Instance spoke.
- Replace legacy eBonding spoke integrations with a more robust and scalable approach.
Getting Started
Before implementing Remote Process Sync, evaluate its capabilities compared to other multi-instance integration options within the ServiceNow AI Platform. Once ready, familiarize yourself with the foundational concepts and configuration steps to build and manage integrations effectively.
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.
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.
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
| 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
- 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.
- 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
When you're ready to start building and managing a Remote Process Sync integration, learn the basics of Getting started with Remote Process Sync.