---
schema_version: "1"
id: 173571b1ad1914971ed0b64ded62bff6eb6b2d521424fe7f2b148f0d0f56459d
title: Batch Action for Integration Procedures (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_batch_action_for_integration_procedures.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_batch_action_for_integration_procedures.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2d4330f0cf720ef806ba7132435c80bfe3833fea5212646acf18cd9978c8b434
description: For the managed package runtime, the Batch Action runs a Vlocity Scheduled Job with a Data Source Type of Data Input, Query, List Input, or No Input. A Vlocity scheduled job calls either another Integration Procedure or a VlocityOpenInterface.
products:
  - Omnistudio
release: "264"
---
# Batch Action for Integration Procedures (Managed Package)

For the managed package runtime, the Batch Action runs a Vlocity Scheduled Job with a **Data Source Type** of **Data Input**, **Query**, **List Input**, or **No Input**. A Vlocity scheduled job calls either another Integration Procedure or a VlocityOpenInterface.

![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

The format of the input that the Scheduled Job sends to the Integration Procedure or VlocityOpenInterface it invokes differs based on the **Is Input As List** and **Batch Size** job fields. The original input to the Batch Action is passed in under a `vlcInputMap` JSON node.

For example, suppose the job has a **Data Source Type** of **Query** and a query that selects Accounts. And suppose in the Batch Action's input you specify a Key of `CompanyName` and a Value of `Acme`. If **Is Input As List** is not checked in the job configuration, the input that the Scheduled Job sends looks like this:

```
{"Id": "00161000015IvYnAAK", "vlcInputMap": {"CompanyName": "Acme"}} 
```

If **Is Input As List** is checked and the **Batch Size** is 1 in the job configuration, the input looks like this, with a `records` node for the list:

```
{"records": [{"Id": "00161000015IvYnAAK"}], "vlcInputMap": {"CompanyName": "Acme"}}
```

If **Is Input As List** is checked and the **Batch Size** is 2, the input looks like this, again with a `records` node for the list:

```
{"records": [{"Id": "00161000015IvYnAAK"}, {"Id": "001610000050IKQAA2"}], "vlcInputMap": {"CompanyName": "Acme"}}
```

If the **Data Source Type** is **List Input**, see the following example for an explanation of the input that the Scheduled Job sends to the Integration Procedure.

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_tip.png)

Tip

If the **Data Source Type** is set to **List Input** or if **Is Input As List** is checked, the input must be in list format even if the list contains only one item. Omnistudio Data Mapper Extracts that return a list with one item often convert it to a single object. To convert a single object back into a list, you can use the first example in [Omnistudio Data Mapper Transform Examples (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_dataraptor_transform_examples.htm&release=264.0.0&type=5 "For the managed package runtime, Data Mapper Transform examples demonstrate how to convert a single item into a list with one item and how to convert a list of objects to a list of values.").

The Integration Procedure doesn't wait for the job that its Batch Action calls to finish. However, the Batch Action returns the Id of the Apex batch job in the `ApexJobId` node of the Integration Procedure's output JSON.

- **[Batch Action Properties for Integration Procedures (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_batch_action_properties_for_integration_procedures.htm&release=264.0.0&type=5)**  
    For the managed package runtime, these properties are unique to or function in a unique manner in Batch Actions. The Batch Action runs a Vlocity Scheduled Job with a **Data Source Type** of **Data Input**, **Query**, **List Input**, or **No Input**. A Vlocity Scheduled Job calls either another Integration Procedure or a VlocityOpenInterface.
- **[Workflow for Batch Action Example (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_workflow_for_batch_action_example.htm&release=264.0.0&type=5)**  
    For the managed package runtime, one Integration Procedure uses a Batch Action to invoke a Vlocity Scheduled Job, which invokes a second Integration Procedure on a schedule.