Remote Process Sync Inbound Flow Template - Basic

  • Release version: Xanadu
  • Updated August 1, 2024
  • 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 Remote Process Sync Inbound Flow Template - Basic

    This document describes a sample Remote Process Sync subflow designed for processing incoming payloads from a remote instance. It establishes a correlation between a remote record and a local incident record. Customers can copy and customize this subflow to fit their specific incident management needs.

    Show full answer Show less

    Key Features

    • Global Availability: Accessible as a Global Remote Process Sync subflow.
    • Integration Hub Requirement: This action requires an Integration Hub subscription for functionality.
    • Role Requirements: Necessary roles must be granted via delegated development or assigned to the user.
    • Dynamic Inputs: Users can input values and utilize dynamic options from the Data panel.

    Inputs

    • Wait for Completion: True/False option to pause the parent flow until the subflow completion.
    • Remote System: A record reference for the remote instance involved in process synchronization.
    • Remote Correlation ID: A unique identifier for correlation on the remote instance.
    • Local Correlation ID: A unique identifier for correlation on the local instance.
    • Process Event: The name of the process event to execute, consistent across instances.
    • Payload: A JSON string detailing changes from a remote instance, transformed into an object locally.
    • CRUD Operation: Indicates the database operation that triggered the event (Create, Update, or Delete).

    Outputs

    • Error Message: Displays any error returned by the action.
    • Status: Indicates the synchronization state of records (Active or Inactive).

    This subflow enables ServiceNow customers to effectively synchronize processes between local and remote instances, ensuring accurate and timely updates across systems.

    A sample Remote Process Sync subflow to process incoming payloads received from a remote instance. This subflow creates a correlation between a remote record and a local incident record. Copy this subflow and edit the actions that refer to the Incident table.

    Roles and availability

    Available as a Global Remote Process Sync subflow.

    Subscription requirements
    This action requires an Integration Hub subscription. For more information, see Request Integration Hub and Legal schedules - IntegrationHub overview.
    Role requirements
    This action requires roles granted by delegated development or assigned to the user. For more information, see User access to Workflow Studio flows.

    Inputs

    Provide a value for each input that your action needs. To add dynamic values, you can also drag pills from the Data panel or select them from the pill picker.

    Wait for Completion
    Data type: True/False

    Option to require the parent flow to wait for the subflow to complete. If enabled, the parent flow cannot proceed to the next action until the subflow completes.

    Remote System
    Data type: Record

    Reference to the Process Sync Remote System record for the remote instance you are synchronizing processes with. This record identifies the instance that receives outbound synchronization changes or that sent inbound synchronization changes.

    Remote Correlation ID
    Data type: String

    Globally unique ID of a correlation on a remote instance you are synchronizing processes with. This ID uniquely identifies the correlation for outbound transactions.

    Local Correlation ID
    Data type: String

    Globally unique ID of a correlation on the local instance you are synchronizing processes with. This ID uniquely identifies the correlation for inbound transactions.

    Process Event
    Data type: String

    Name of the process event to run. The name is the same on each instance that participates in process synchronization. For example, case-to-incident.

    Payload
    Data type: String

    JSON string containing changes generated on a remote instance. For example, a list of field changes for a case record from a remote instance. The system transforms this JSON string to an object on the local instance.

    CRUD Operation
    Data type: Choice

    Database operation that triggered the process event. The available options are Create, Update, or Delete.

    Outputs

    These outputs appear in the Data panel. You can use them as inputs elsewhere in your flow.

    Error Message
    Data type: String

    Error returned by the action.

    Status
    Data type: Choice

    Synchronization state of records. The available options are Active or Inactive. Active records are being synchronized. Inactive records are not synchronized.