> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arc.cdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Excel Connector

> The Excel connector converts data between Excel sheets (.xlsx) and XML files using Table or Template modes.

export const SlasTab = ({siteName = "CData Arc"}) => <>
    <p><em>Settings related to configuring Service Level Agreements (SLAs).</em></p>
    <p>
      SLAs enable you to configure the volume you expect connectors in your flow to send or receive, and to set the time frame in which you expect that volume to be met. {siteName} sends emails to warn the user when an SLA is not met, and marks the SLA as <em>At Risk</em>, which means that if the SLA is not met soon, it will be marked as <em>Violated</em>. This gives the user an opportunity to step in and determine the reasons the SLA is not being met, and to take appropriate actions. If the SLA is still not met at the end of the at-risk time period, the SLA is marked as violated, and the user is notified again.
    </p>
    <p>
      To define an SLA, toggle <strong>Expected Volume</strong> on, then click the <strong>Settings</strong> tab.
    </p>
    <img src="/public/images/sla_empty.png" alt="SLA Empty" />
    <ul>
      <li>If your connector has separate send and receive actions, use the radio buttons to specify which direction the SLA pertains to.</li>
      <li>In the <strong>Expect at least</strong> portion of the window:
        <ul>
          <li>Set the minimum number of transactions you expect to be processed (the volume)</li>
          <li>Use the <strong>Every</strong> fields to specify the time frame</li>
          <li>Indicate when the SLA should go into effect. If you choose <strong>Starting on</strong>, complete the date and time fields.</li>
          <li>Check the boxes for the days of the week that you want the SLA to be in effect. Use the dropdown to choose <strong>Everyday</strong> if necessary.</li>
        </ul>
      </li>
      <li>In the <strong>Set status to 'At Risk'</strong> portion of the window, specify when the SLA should be marked as at risk.
        <ul>
          <li>By default, notifications are not sent until an SLA is in violation. To change that, check <strong>Send an 'At Risk' notification</strong>.</li>
        </ul>
      </li>
    </ul>
    <p>
      The following example shows an SLA configured for a connector that expects to receive 1000 files every day Monday-Friday. An at-risk notification is sent 1 hour before the end of the time period if the 1000 files have not been received.
    </p>
    <img src="/public/images/sla_defined.png" alt="SLA Configuration Example" />
    <Note>
      You can turn off SLA alerts if necessary. This can be useful during maintenance windows. Click <strong>Settings</strong> on the navbar, then navigate to <strong>Alerts &gt; General Alerts</strong>. Click the tablet and pencil icon to edit, and uncheck the <strong>SLA Alerts</strong> setting.
    </Note>
  </>;

export const AlertsTab = ({siteNameShort = "Arc"}) => <>
    <p><em>Settings related to configuring alerts.</em></p>
    <p>
      Before you can execute Service Level Agreements (SLAs), you need to set up email alerts for notifications. By default, {siteNameShort} uses the global settings on the <a href="/26.3/self-hosted/en/getting-started/administration/settings/alerts">Alerts</a> tab. To use other settings for this connector, toggle <strong>Override global setting</strong> on.
    </p>
    <p>
      By default, error alerts are enabled, which means that emails are sent whenever there is an error. To turn them off, uncheck the <strong>Enable</strong> checkbox.
    </p>
    <p>
      Enter a <strong>Subject</strong> (mandatory). Check <strong>Allow {siteNameShort}Script in Subject</strong> to use {siteNameShort}Script in the <strong>Subject</strong> field. When you select this, the <strong>{siteNameShort}Script Editor</strong> button appears (<img src="/public/images/rest_arcscript_editor.png" alt="arcscript editor button" style={{
  display: 'inline',
  verticalAlign: 'middle',
  margin: 0
}} />).
    </p>
    <p>
      Optionally, enter a comma-separated list of <strong>Recipient</strong> emails.
    </p>
  </>;

export const Message = () => <>
    <p><em>Message settings determine how the connector searches for messages and manages them after processing.</em></p>
    <p><strong>Note:</strong> The settings below are deprecated and hidden by default. They appear only on connectors where they were previously enabled or configured to a non-default value. To retain copies of successfully processed files, right-click the connector in the flow, choose <strong>Show Success Path</strong>, and connect the success path to a <a href="/26.3/self-hosted/en/connectors/file">File connector</a>.</p>
    <table>
      <thead>
        <tr><th>Setting</th><th>Description</th></tr>
      </thead>
      <tbody>
        <tr>
          <td><strong>Save to Sent Folder</strong> (Deprecated)</td>
          <td>Copies files processed by the connector to the Sent folder. Disabled by default. Files saved to the Sent folder are not covered by <a href="/26.3/self-hosted/en/getting-started/administration/settings/encryption-at-rest">Encryption at Rest</a>.</td>
        </tr>
        <tr>
          <td><strong>Sent Folder Scheme</strong> (Deprecated)</td>
          <td>Groups files in the <strong>Sent</strong> folder by the selected time interval. Only relevant when <strong>Save to Sent Folder</strong> is enabled.</td>
        </tr>
      </tbody>
    </table>
  </>;

export const MiscConnector = () => <>
    <p><em>Miscellaneous settings are for specific use cases.</em></p>
    <table>
      <thead>
        <tr>
          <th>Setting</th>
          <th>Description</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <td><strong>Other Settings</strong></td>
          <td>Enables you to configure hidden connector settings in a semicolon-separated list (for example, <code>setting1=value1;setting2=value2</code>). Normal connector use cases and functionality should not require the use of these settings.</td>
        </tr>
      </tbody>
    </table>
  </>;

export const Logging = () => <>
    <p><em>Settings that govern the creation and storage of logs.</em></p>
    <table>
      <thead>
        <tr>
          <th>Setting</th>
          <th>Description</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <td><strong>Log Level</strong></td>
          <td>The verbosity of logs generated by the connector. When you request support, set this to <strong>Debug</strong>.</td>
        </tr>
        <tr>
          <td><strong>Log Subfolder Scheme</strong></td>
          <td>Instructs the connector to group files in the Logs folder according to the selected interval. The <strong>Weekly</strong> option (which is the default) instructs the connector to create a new subfolder each week and store all logs for the week in that folder. Leaving this setting blank tells the connector to save all logs directly in the Logs folder. For connectors that process many transactions, using subfolders helps keep logs organized and improves performance.</td>
        </tr>
        <tr>
          <td><strong>Log Messages</strong></td>
          <td>Check this to have the log entry for a processed file include a copy of the file itself. If you disable this, you might not be able to download a copy of the file from the <strong>Transactions</strong> tab.</td>
        </tr>
      </tbody>
    </table>
  </>;

export const MacrosExamples = ({extraMacros = []}) => <>
    <p>
      Some macros, such as %Ext% and %ShortDate%, do not require an argument, but others do. All
      macros that take an argument use the following syntax: <code>%Macro:argument%</code>
    </p>

    <p>Here are some examples of the macros that take an argument:</p>

    <ul>
      <li>%Header:headername%: Where <code>headername</code> is the name of a header on a message.</li>
      <li>%Header:mycustomheader% resolves to the value of the <code>mycustomheader</code> header set on the input message.</li>
      <li>%Header:ponum% resolves to the value of the <code>ponum</code> header set on the input message.</li>
      <li>%RegexFilename:pattern%: Where <code>pattern</code> is a regex pattern. For example, <code>%RegexFilename:^([\w][A-Za-z]+)%</code> matches and resolves to the first word in the filename and is case insensitive (<code>test_file.xml</code> resolves to <code>test</code>).</li>
      <li>%Vault:vaultitem%: Where <code>vaultitem</code> is the name of an item in the <a href="/26.3/self-hosted/en/getting-started/administration/settings/global-settings-vault">vault</a>. For example, <code>%Vault:companyname%</code> resolves to the value of the <code>companyname</code> item stored in the vault.</li>
      <li>%DateFormat:format%: Where <code>format</code> is an accepted date format (see <a href="/26.3/self-hosted/en/scripting/value-formatters/date-formatters#sample-date-formats">Sample Date Formats</a> for details). For example, <code>%DateFormat:yyyy-MM-dd-HH-mm-ss-fff%</code> resolves to the date and timestamp on the file.</li>
      {extraMacros.filter(item => item.example).map(item => <li key={`ex-${item.name}`}>{item.example}</li>)}
    </ul>

    <p>You can also create more sophisticated macros, as shown in the following examples:</p>

    <ul>
      <li>Combining multiple macros in one filename: <code>%DateFormat:yyyy-MM-dd-HH-mm-ss-fff%%EXT%</code></li>
      <li>Including text outside of the macro: <code>MyFile_%DateFormat:yyyy-MM-dd-HH-mm-ss-fff%</code></li>
      <li>Including text within the macro: <code>%DateFormat:'DateProcessed-'yyyy-MM-dd_'TimeProcessed-'HH-mm-ss%</code></li>
    </ul>
  </>;

export const MacrosTable = ({siteName = "CData Arc", extraMacros = []}) => <>
    <p>
      Using macros in file naming strategies can enhance organizational efficiency and contextual
      understanding of data. By incorporating macros into filenames, you can dynamically include
      relevant information such as identifiers, timestamps, and header information, providing
      valuable context to each file.
    </p>

    <p>{siteName} supports these macros, which all use the following syntax: <code>%Macro%</code>.</p>

    <table>
      <thead>
        <tr><th>Macro</th><th>Description</th></tr>
      </thead>
      <tbody>
        <tr><td>ConnectorID</td><td>Evaluates to the ConnectorID of the connector.</td></tr>
        <tr><td>ConnectorName</td><td>Evaluates to the name of the connector. Enables you to include the connection name in file names or paths: for example, to tag backup files by which database connection produced them.</td></tr>
        <tr><td>Ext</td><td>Evaluates to the file extension of the file currently being processed by the connector.</td></tr>
        <tr><td>Filename</td><td>Evaluates to the filename (extension included) of the file currently being processed by the connector.</td></tr>
        <tr><td>FilenameNoExt</td><td>Evaluates to the filename (without the extension) of the file currently being processed by the connector.</td></tr>
        <tr><td>MessageId</td><td>Evaluates to the MessageId of the message being output by the connector.</td></tr>
        <tr><td>RegexFilename:<em>pattern</em></td><td>Applies a RegEx pattern to the filename of the file currently being processed by the connector.</td></tr>
        <tr><td>Header:<em>headername</em></td><td>Evaluates to the value of a targeted header (<code>headername</code>) on the current message being processed by the connector.</td></tr>
        <tr><td>LongDate</td><td>Evaluates to the current datetime of the system in long-handed format (for example, Wednesday, January 24, 2024).</td></tr>
        <tr><td>ShortDate</td><td>Evaluates to the current datetime of the system in a yyyy-MM-dd format (for example, 2024-01-24).</td></tr>
        <tr><td>DateFormat:<em>format</em></td><td>Evaluates to the current datetime of the system in the specified format (<code>format</code>). See <a href="/26.3/self-hosted/en/scripting/value-formatters/date-formatters#date-formats-with-literal-characters">Sample Date Formats</a> for the available datetime formats.</td></tr>
        <tr><td>Vault:<em>vaultitem</em></td><td>Evaluates to the value of the specified vault item.</td></tr>
        {extraMacros.map(item => <tr key={item.name}>
            <td>{item.name}</td>
            <td>{item.description}</td>
          </tr>)}
      </tbody>
    </table>
  </>;

export const Performance = () => <>
    <p><em>Settings related to the allocation of resources to the connector.</em></p>
    <table>
      <thead>
        <tr>
          <th>Setting</th>
          <th>Description</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <td><strong>Max Workers</strong></td>
          <td>The maximum number of worker threads consumed from the threadpool to process files on this connector. If set, this overrides the default setting on the <a href="/26.3/self-hosted/en/getting-started/administration/settings/performance-settings">Performance Settings</a> portion of the <a href="/26.3/self-hosted/en/getting-started/administration/settings/advanced-settings">Advanced Settings</a> page.</td>
        </tr>
        <tr>
          <td><strong>Max Files</strong></td>
          <td>The maximum number of files sent by each thread assigned to the connector. If set, this overrides the default setting on the <a href="/26.3/self-hosted/en/getting-started/administration/settings/performance-settings">Performance Settings</a> portion of the <a href="/26.3/self-hosted/en/getting-started/administration/settings/advanced-settings">Advanced Settings</a> page.</td>
        </tr>
      </tbody>
    </table>
  </>;

export const siteNameShort = "Arc";

export const siteName = "CData Arc";

The Excel connector converts data between Excel sheets (.xlsx) and XML files.

## Key Capabilities

* Bidirectional Excel/XML conversion in both Table and Template modes
* Advanced template system using ArcScript for dynamic data population
* Support for multiple worksheets with configurable row/column ranges

## Overview

Excel connectors can be configured in two modes: [Table](#table-mode) and [Template](#template-mode). These modes are described below.

### Table Mode

The default mode for Excel connectors is **Table**. This mode only supports converting files from XLSX to XML. To convert from XML to XSLX, use **Template** mode.

In Table mode, the connector treats input XLSX files exactly like CSV files. The resulting output XML file has the following structure, where each row (record) in the original file becomes a child of the root element **Items**:

```xml theme={null}
<Items>
 <Record>
  <field_0></field_0>
  <field_1></field_1>
  <field_2></field_2>
 </Record>
</Items>
```

### Template Mode

In **Template** mode, the connector uses a template file to perform conversions. This template file matches the output file format:

* When converting from XML to Excel, the template file is an Excel file.
* When converting from Excel to XML, the template file is an XML file.

These template files use {siteNameShort}Script to dynamically populate the output files with data from the input files. For more information, see the [Templates](#templates) section.

## Connector Configuration

This section contains all of the configurable connector properties.

### Settings Tab

#### Configuration

*Settings related to the core configuration of the connector.*

| Setting                   | Description                                                                                                                                                                                                                            |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Connector Id**          | The static, unique identifier for the connector.                                                                                                                                                                                       |
| **Connector Type**        | Displays the connector name and a description of what it does.                                                                                                                                                                         |
| **Connector Description** | An optional field to provide a free-form description of the connector and its role in the flow.                                                                                                                                        |
| **Translation Mode**      | Specify which method (**Table** or **Template**) to use to translate the input file to the output format. See the [Overview](#overview) for more information.                                                                          |
| **Column headers**        | (Table mode) Check this to have the translation use the values in the first row of the XLSX file as the element names of the child elements. If unchecked, the value elements are given generic names such as field\_0, field\_1, etc. |
| **Template File**         | (Template mode) The file that functions as the output template. Data is dynamically added to the file based on the scripting in the template. See the [Templates](#templates) section for details.                                     |

#### Advanced Settings

*Settings not included in the previous categories.*

| Setting                          | Description                                                                                                                                                                                                                                                                    |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Start Row**                    | (Table mode) The first row in the sheet to use for the output table.                                                                                                                                                                                                           |
| **Start Column**                 | (Table mode) The first column in the sheet to use for the output table.                                                                                                                                                                                                        |
| **End Column**                   | (Table mode) The last column in the sheet to use for the output table. If not set, the column preceding the first empty cell on the first row is detected as the end of the sheet.                                                                                             |
| **DateTime Format**              | (Table mode) The format to use for DateTime values in the Excel document.                                                                                                                                                                                                      |
| **Number Format**                | (Table mode) The format to use for numbers in the Excel document. Set this if you want all numbers in the document to be handled in the same way.                                                                                                                              |
| **Propagate Merged Cell Values** | (Table mode) When reading Excel in table mode, check this to propagate the value of each merged cell to all rows in the merged area. This option provides more complete data but it requires an extra read of the Excel file, which can affect performance on large workbooks. |
| **Local File Scheme**            | A scheme for assigning filenames to messages that are output by the connector. You can use macros in your filenames dynamically to include information such as identifiers and timestamps. For more information, see [Macros](#macros).                                        |

### Advanced Tab

#### Message

<Message />

#### Logging

<Logging />

#### Other Settings

| Setting              | Description                                                                                                                                                                                                                                                                                                  |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Processing Delay** | The amount of time (in seconds) by which the processing of files placed in the **Transactions** tab is delayed. This is a legacy setting. Best practice is to [use a File connector](../flows/designing-a-flow#interacting-with-the-local-file-system) to manage local file systems instead of this setting. |

#### Miscellaneous

<MiscConnector />

### Automation Tab

*Settings related to the automatic processing of files by the connector.*

#### Automation Settings

| Setting  | Description                                                             |
| -------- | ----------------------------------------------------------------------- |
| **Send** | Whether messages arriving at the connector are automatically processed. |

#### Performance

<Performance />

### Alerts Tab

<AlertsTab />

### SLAs Tab

<SlasTab />

## Templates

### XML to Excel

The following snippet from an XML file contains a list of elements under the `/Items/Orders` path.

```xml theme={null}
<Items>
    <Orders>
        <OrderNo>PO0012345</OrderNo>
        <Customer>Teddy</Customer>
        <Date>04/19/2023</Date>
        <SubTotal>23.98</SubTotal>
        <Items>
            <Name>Teddy Bear</Name>
            <Cost>14.99</Cost>
            <Desc>Brown</Desc>
        </Items>
        <Items>
            <Name>Truck</Name>
            <Cost>8.99</Cost>
            <Desc>Red</Desc>
        </Items>
    </Orders>
</Items>
```

To convert this XML file to XSLX, you must create an Excel template. The image below shows an example Excel template that uses *xmlDOMSearch* and *xpath* to loop through the elements of the XML file:

<img src="https://mintcdn.com/cdata-arc/j59334epfVQRoK96/public/images/simple_excel_template.png?fit=max&auto=format&n=j59334epfVQRoK96&q=85&s=4b28801507eff617c2864b5300a893c8" alt="Simple Template" width="874" height="183" data-path="public/images/simple_excel_template.png" />

Every Excel template must contain the following elements, which are shown in the example above:

* Static column headers. In the example above, this is **Order Detail**.
* Scripting in Excel notes. This scripting should use the [xmlDOMSearch](#xmldomsearch) operation to loop through the input XML at a specified XPath. In the example above, this is contained in the **arc:call** operation.
* Scripting in Excel cells. This scripting should use the [xpath formatters](#xpath-formatters) to read values from the XML at a given xpath. This xpath is relative to the xpath specified in the *xmlDOMSearch* operation.

The details of the *xmlDOMSearch* operation and *xpath* formatters in this example are described below.

#### xmlDOMSearch

The *xmlDOMSearch* requires two parameters:

| Parameter | Description                                                                                                                                                                                                                                                                                                                                                                                     |
| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **URI**   | The resource path to the XML file to parse. The `[filepath]` attribute resolves to the input XML file to the connector, and the URI should almost always be set to this value. In the above example, the filepath is URL-encoded with the *urlencode* formatter to ensure that special characters in the filepath do not prevent the connector from reading the file: `[filepath \| urlencode]` |
| **xpath** | The XML path to loop over in the document. The operation loops for each occurrence of the specified xpath. For example, with the xpath `/Items/Orders`, each *Orders* element that is a child of the root *Items* element causes a new set of output in the resulting Excel file.                                                                                                               |

#### xpath formatters

The Excel notes with the *xmlDOMSearch* operation surround a block of cells that reference the input XML via the *xpath* formatter. The *xpath* formatter reads values from the input XML at the specified xpath.

<Note>This *xpath* is relative to the path provided as a parameter to the *xmlDOMSearch* operation.</Note>

In the above example, the first cell is populated with: `[xpath("OrderNo")]`. Since this xpath is relative, the cell is populated with the value from the following path in the input XML: `/Items/Orders/OrderNo`.

If the *xmlDOMSearch* operation loops more than once—that is, if more than one instance of the operation's xpath parameter is found—then the block of cells between the Excel notes is repeated. The new cells are added vertically, so in the above example the second *OrderNo* cell would be directly below the first *Notes* cell.

### Excel to XML

To convert from XSLX to an XML file, you must create a custom XML template using {siteNameShort}Script commands. Since XML does not support the same scripting functionality as Excel files, the structure and formatting for converting from XSLX to XML is different than from XML to Excel.

<Note>Due to the wide range of potential input and output structures, there is no universal solution for every conversion need. The example template shown below is just one of many potential solutions. You need to create a template based on your own needs.</Note>

This example template uses a combination of standard XML syntax and {siteNameShort} Script to read, process, and convert data from an input Excel file.

The `arc:set` lines below specify the location of the file and the Excel version used to create the file.

```xml theme={null}
<!-- Read Excel -->
<arc:set attr="xml.file" value="[FilePath]" />
<arc:set attr="xml.version" value="2007" />
```

The sections below specify the conversion parameters and map the headers into standard XML formatting.

The parameter `[_value | toalphanum | replace(' ','')]` indicates that the `arc:set` command should parse header names from the Excel file, convert them to alphanumeric format, eliminate blank spaces, and assign them as headers in the XML file.

```xml theme={null}
<!-- Always use first sheet-->
<arc:call op="excelListSheets" in ="xml" out="sheet">
  <arc:set attr="xml.sheet" value="[sheet.sheet]" />
  <arc:break />
</arc:call>

<!-- read the headers into an array-->
<arc:set attr="xml.map:headers" value="A1:*1" />
<arc:call op="excelGet" in="xml" out="header">
  <arc:enum attr="header.headers#">
    <arc:set attr="data.headernames#" value="[_value | toalphanum | replace(' ','')]" />
  </arc:enum>
</arc:call>

<arc:set attr="_log.info" value="[data.headernames#1]" />

<arc:enum range="A..Z">
  <arc:set attr="tmp.cells#" value="[_value]" />
</arc:enum>
```

The sections below process the remaining data and build the data columns according to the specified structure.

```xml theme={null}
<!-- read the remaining cells -->
<arc:enum attr="data.headernames#">
  <arc:set attr="xml.map:[_value]" value="[tmp.cells#[_index]]2:[tmp.cells#[_index]]*" />
</arc:enum>

<!-- build the columns -->
<arc:call op="excelGet" in="xml" out="cols">
  <arc:map from="cols" to="data" map="*=*" />
</arc:call>

<Items>
  <arc:enum attr="data.[data.headernames#1]#"><arc:set attr="tmp.colIndex" value="[_index]" />
    <Record>
      <arc:enum attr="data.headernames#">
        <[_value]>[data.[_value]#[tmp.colIndex] | def]</[_value]>
      </arc:enum>
    </Record>
  </arc:enum>
</Items>
```

## Macros

<MacrosTable />

### Examples

<MacrosExamples />

## Excel Operations

In addition to the Operations provided with {siteNameShort}, connectors can provide operations that extend functionality into {siteNameShort}Script.

These connector operations can be called just like any other {siteNameShort}Script operation, except for two details:

1. They must be called through the `connector.rsc` endpoint.
2. They must include an auth token.

For example, calling a connector operation using both of these rules might look something like this:

```xml theme={null}
<arc:set attr="in.myInput" value="myvalue" />
<arc:call op="connector.rsc/opName" authtoken="admin:1j9P8v8b9K0x6g5R5t7k" in="in" out="out">
  <!-- handle output from the op here -->
</arc:call>
```

Operations specific to the functionality of the Excel connector are listed below.

### excelClose

Close an Excel connection.

#### Optional Parameters

* **handle**: The handle for the Excel file.

#### Output Attributes

* **success**: True if the connection is closed successfully.

### excelGet

Queries the specified Excel worksheet.

#### Required Parameters

* **sheet**: The name of the Excel worksheet.

#### Optional Parameters

* **version**: The version of Excel you are using. The default is AUTO. You only need to choose another version if you are using a legacy Excel version.
* **file**: The path to the Excel workbook.
* **handle**: The handle for the Excel file.
* **map:\***: This set of inputs contains a mapping of the attribute name and the name of the cell whose value is to be retrieved from the spreadsheet. For example, the attribute name map:MyValue which has a value of C1 pushes an attribute named MyValue with the value found in the cell at C1 in the sheet. You can specify a range of cell names to retrieve a range of cell values.

#### Output Attributes

* **\***: Depends on the content of the sheet and the query specified. If column headers are present they are used to name the output attributes.

### excelListSheets

Lists the worksheets in a specified Excel workbook.

#### Optional Parameters

* **version**: The version of Excel you are using. The default is AUTO. You only need to choose another version if you are using a legacy Excel version.
* **file**: The path to the Excel workbook.
* **handle**: The handle for the Excel file.

#### Output Attributes

* **isHidden**: Returns true if the sheet is hidden from view in Excel.
* **sheet**: The name of the Excel worksheet. Note that the name ends with \$. This is not required when specifying worksheet names to other operations.

### excelOpen

Open an existing Excel workbook.

#### Required Parameters

* **file**: The path to the Excel workbook.

#### Optional Parameters

* **version**: The version of Excel you are using. The default is AUTO. You only need to choose another version if you are using a legacy Excel version.

#### Output Attributes

* **handle**: The handle which is used to execute other operations.