Integration Hub Remote Process Sync
Summarize
Summary of Integration Hub Remote Process Sync
Integration Hub Remote Process Sync enables ServiceNow customers to establish one-way or bidirectional integrations across multiple ServiceNow instances, ensuring that business process workflows remain synchronized. This capability is designed for scenarios where automated processes need to span multiple instances, such as service providers managing workflows for multiple customer instances. It requires an Integration Hub subscription.
Show less
Key Features
- Cross-Instance Workflow Automation: Automate and synchronize workflows across multiple ServiceNow instances to keep all stakeholders updated.
- Data Synchronization: Manage synchronization of records, attachments, and journal fields effectively across instances.
- Order Delivery and Reliability: Uses a standalone correlation engine and queueing system to ensure reliable delivery of data updates in remote instances.
- Error Management: Built-in execution engine within Workflow Studio supports troubleshooting and managing errors or outages in multi-instance processes.
- Domain Separation Support: Supports synchronization in domain-separated environments with specific handling for configuration tables, queue tables, and execution contexts to maintain domain integrity.
Roles and Permissions
Remote Process Sync provides predefined roles to control access and capabilities:
- ihprocesssync: Manage process sync definitions and related records (create, update, delete).
- ihprocesssyncapi: Access only the Remote Process Sync APIs.
- ihprocesssyncrunas: Execute inbound and outbound flows tied to process sync definitions, requiring access to affected tables.
Practical Considerations for ServiceNow Customers
- Integration Choice: Remote Process Sync is suited for complex multi-instance integrations that involve high-level business processes, differentiating it from simpler data replication or Remote Instance spoke solutions.
- Replacement for eBonding Spoke: It supersedes the eBonding spoke for instance integration purposes.
- Getting Started: Customers should familiarize themselves with the basics of Remote Process Sync before building integrations to understand its framework and capabilities fully.
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.