Key Capabilities
- XSLT 1.0 transformation support for converting XML documents based on stylesheet templates
- Document function and embedded script support for advanced transformations
Overview
After an XSLT file has been uploaded to the connector, XML files arriving at the connector are automatically converted based on the XSLT definition.Connector Configuration
This section contains all of the configurable connector properties.Settings Tab
Connector Settings
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. |
| XSL Template File | The XSLT file that defines the XML transformation to be performed by the connector. |
Other Settings
Settings not included in the previous categories. Only visible if you use the .NET edition.| Setting | Description |
|---|---|
| Document Function | Check this to allow use of the document() function while processing XSLT. |
| Embedded Scripts | Check this to allow use of embedded scripts while processing XSLT. |
Advanced Tab
Advanced Settings
| Setting | Description |
|---|---|
| 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) 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 to manage local file systems instead of this setting. |
Message
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 to manage local file systems instead of this setting. |
Miscellaneous
Automation Tab
Automation Settings
Settings related to the automatic processing of files by the connector.| Setting | Description |
|---|---|
| Send | Whether messages arriving at the connector are automatically processed. |
Performance
Alerts Tab
SLAs Tab
Macros
Examples
XSLT Operations
In addition to the Operations provided with , connectors can provide operations that extend functionality into Script. These connector operations can be called just like any other Script operation, except for two details:- They must be called through the
connector.rscendpoint. - They must include an auth token.
xsltTranslate
Translates an input XML file according to a configured XSLT connector or a specified XSLT file.Required Parameters
- ConnectorId: The name of the configured XSLT connector to use for translation, OR
- TemplateFile: The path to the XSL template to use for translation, OR
- Data: The contents of the XSL template to use for translation
- File: The input file to translate
Optional Parameters
- OutputEncoding: By default, the operation outputs ASCII data. To output base64-encoded binary data instead, set this parameter to
base64. - OutputFile: When this is set, output data is not written to the Data output attribute and is instead written to the specified file.
Output Attributes
- Data: The output from the translation is passed through this parameter.