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.Message
Message settings determine how the connector searches for messages and manages them after processing.
Note: 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 Show Success Path, and connect the success path to a File connector.
| Setting | Description |
|---|---|
| Save to Sent Folder (Deprecated) | Copies files processed by the connector to the Sent folder. Disabled by default. Files saved to the Sent folder are not covered by Encryption at Rest. |
| Sent Folder Scheme (Deprecated) | Groups files in the Sent folder by the selected time interval. Only relevant when Save to Sent Folder is enabled. |
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.Performance
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 usexsubtree, 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:
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 and the script [xsubtree(Sub)] on a destination node produces the following output:
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.