XML Map Configuration

XML Map Tab

Use this tab to upload your source and destination template files, and to build your mappings. See Configure the Mapping in the Mapping documentation for detailed instructions on how to use the mapping editor.

Settings Tab

Connector Configuration

Settings related to the core operation 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.

Advanced Tab

AI

Advanced Settings

Advanced file processing settings.

Setting	Description
XML Declaration	Specify whether to include the XML declaration in generated XML files.
Cache Content	Specify whether the parser should cache the original raw content of each XML element so it can be retrieved by `xsubtree` during mapping. This increases memory usage but allows mappings to copy the original content of subtrees verbatim. See Copying XML Subtrees for details.
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.
Processing Delay	The amount of time (in seconds) the connector waits before processing a file.

Logging

Settings that govern the creation and storage of logs.

Setting	Description
Log Level	The verbosity of logs generated by the connector. When you request support, set this to Debug.
Log Subfolder Scheme	Instructs the connector to group files in the Logs folder according to the selected interval. The Weekly 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.
Log Messages	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 Transactions tab.

Miscellaneous

Miscellaneous settings are for specific use cases.

Setting	Description
Other Settings	Enables you to configure hidden connector settings in a semicolon-separated list (for example, `setting1=value1;setting2=value2`). Normal connector use cases and functionality should not require the use of these settings.

Automation Tab

Automation Settings

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

Setting	Description
Send	A toggle that instructs the connector to automatically send files when they are ready.

Performance

Setting	Description
Max Workers	The maximum number of worker threads consumed from the threadpool.
Max Files	The maximum number of files sent by each thread.

Alerts Tab

Before you can execute Service Level Agreements (SLAs), you need to set up email alerts for notifications. By default, Arc uses the global settings on the Alerts tab. To use other settings for this connector, toggle Override global setting on. By default, error alerts are enabled, which means that emails are sent whenever there is an error. To turn them off, uncheck the Enable checkbox. Enter a Subject (mandatory), then optionally enter a comma-separated list of Recipient emails.

SLAs Tab

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. CData Arc sends emails to warn the user when an SLA is not met, and marks the SLA as At Risk, which means that if the SLA is not met soon, it will be marked as Violated. To define an SLA, toggle Expected Volume on, then click the Settings tab.

If your connector has separate send and receive actions, use the radio buttons to specify which direction the SLA pertains to.
In the Expect at least portion of the window, set the minimum number of transactions you expect to be processed, use the Every fields to specify the time frame, indicate when the SLA should go into effect, and check the boxes for the days of the week.
In the Set status to ‘At Risk’ portion of the window, specify when the SLA should be marked as at risk. Check Send an ‘At Risk’ notification to receive notifications before violation.

You can turn off SLA alerts during maintenance windows. Click Settings on the navbar, then navigate to Alerts > General Alerts. Click the tablet and pencil icon to edit, and uncheck the SLA Alerts setting.

Copying XML Subtrees (xsubtree)

The xsubtree formatter copies the original raw XML content of a source element verbatim to the destination, preserving the full subtree structure without re-serializing it through the mapping engine. This is useful when part of a source document needs to pass through unchanged, regardless of its internal structure. To use xsubtree, first enable Cache Content on the Advanced tab. This instructs the parser to retain the original raw content of each XML element so that xsubtree can retrieve it. Enabling this setting increases memory usage proportionally to the size of the source document. Once Cache Content is enabled, use the xsubtree formatter in a custom script on a destination node:

[xsubtree(ElementName)]

Where ElementName is the name (or relative XPath) of the source element whose subtree you want to copy.

Example

Given the following source document:

<Items>
  <Item>
    <Sub>
      <X>1</X>
      <Y>2</Y>
    </Sub>
  </Item>
  <Item>
    <Sub>
      <A>Hello</A>
      <B>World</B>
    </Sub>
  </Item>
  <Item>
    <Sub>
      <Name>Test</Name>
    </Sub>
  </Item>
</Items>

A mapping with a Foreach loop over /Items/Item and the script [xsubtree(Sub)] on a destination node produces the following output:

<Out xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Result><Sub><X>1</X><Y>2</Y></Sub></Result>
  <Result><Sub><A>Hello</A><B>World</B></Sub></Result>
  <Result><Sub><Name>Test</Name></Sub></Result>
</Out>

Each Sub element is copied exactly as it appears in the source, including all child elements, regardless of how they differ between iterations.

If a specified element does not exist in the source, xsubtree returns an empty result.

Macros

Macro	Description
ConnectorID	The Connector ID of the connector.
Ext	The file extension of the file (e.g., `xml`, `csv`).
Filename	The original filename of the message.
FilenameNoExt	The original filename of the message, without the file extension.
MessageId	The unique identifier assigned to the message.
RegexFilename	A filename derived from a regex on the original filename.
Header	The value from a message header, referenced by name.
LongDate	The current date/time in long format.
ShortDate	The current date/time in short format.
DateFormat	The current date/time in a custom format.
Vault	The value from a vault entry, referenced by name.

Getting Started

Flows

EDI Trading Partner Management Console

Connectors

Mapping

APIs and Automation

How-To Guides

Scripting

Software License and Third-Party Copyrights

XML Map Tab

Settings Tab

Connector Configuration

Advanced Tab

AI

Advanced Settings

Logging

Miscellaneous

Automation Tab

Automation Settings

Performance

Alerts Tab

SLAs Tab

Copying XML Subtrees (xsubtree)

Example

Macros

​XML Map Tab

​Settings Tab

​Connector Configuration

​Advanced Tab

​AI

​Advanced Settings

​Logging

​Miscellaneous

​Automation Tab

​Automation Settings

​Performance

​Alerts Tab

​SLAs Tab

​Copying XML Subtrees (xsubtree)

​Example

​Macros

XML Map Tab

Settings Tab

Connector Configuration

Advanced Tab

AI

Advanced Settings

Logging

Miscellaneous

Automation Tab

Automation Settings

Performance

Alerts Tab

SLAs Tab

Copying XML Subtrees (xsubtree)

Example

Macros