{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":21702,"path":"integrate-applications/integration-hub-remote-process-sync/rps-sample-outbound-incident-subflow.md","title":"Remote Process Sync Outbound Flow Template - Basic","bundle":null,"doc_type":null,"release":"australia","body":"\n# Remote Process Sync Outbound Flow Template - Basic\n\nA sample Remote Process Sync subflow to send outgoing payloads to a remote instance. This subflow creates a correlation between a remote record and a local incident record. Copy this subflow and edit the input for the local record to the table of your choice.\n\n## Roles and availability\n\nAvailable as a Global Remote Process Sync subflow.\n\n-   **Subscription requirements**\n\n    This action requires an Integration Hub subscription. For more information, see [Request Integration Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/request-ih-overview.md) and [Legal schedules - IntegrationHub overview](https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/snc-addendum-integrationhub.pdf).\n\n-   **Role requirements**\n\n    This action requires roles granted by delegated development or assigned to the user. For more information, see [User access to Workflow Studio flows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/user-access-flow-designer.md).\n\n\n## Inputs\n\nProvide 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.\n\n-   **Wait for Completion**\n\n    Data type: **True/False**\n\n    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.\n\n-   **Local Record**\n\n    Data type: **Record**\n\n    Reference to a record on the local instance you are synchronizing with another instance. The data pill contains all the field values for the specified record. For example, a case record on the local instance.\n\n-   **Remote System**\n\n    Data type: **Record**\n\n    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.\n\n-   **CRUD Operation**\n\n    Data type: **Choice**\n\n    Database operation that triggered the process event. The available options are Create, Update, or Delete.\n\n-   **Trigger/Capture Definition**\n\n    Data type: **Record**\n\n    Reference to the Capture Definition record that the system uses to create an outbound payload. The data pill contains all the field values for the specified record. For example, a capture definition for case records.\n\n-   **Process Event**\n\n    Data type: **String**\n\n    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.\n\n-   **Payload**\n\n    Data type: **Object**\n\n    Object containing changes generated by a capture definition. For example, a list of field changes for a case record on the local instance. The system transforms this object to a JSON string to send it to a remote instance.\n\n\n## Outputs\n\nThese outputs appear in the Data panel. You can use them as inputs elsewhere in your flow.\n\n-   **Status**\n\n    Data type: **Choice**\n\n    Synchronization state of records. The available options are Active or Inactive. Active records are being synchronized. Inactive records are not synchronized.\n\n-   **Error Message**\n\n    Data type: **String**\n\n    Error returned by the action.\n\n\n"}}