Grenefolc Vartala Ausa — Partner connector operation

The Ausa operation configures data extraction behavior via two primary inputs: the CLI JSON and the XPath JSON.

Options tab

CLI JSON

The CLI JSON controls extraction behavior and diagnostic output during connector execution.

Default configuration:

{
  "cli": {
    "showProcessTrace": false,
    "extractionMode": "value",
    "delimiterChar": "|",
    "errorOnNullSource": false
  }
}

Property	Type	Default	Description
cli.showProcessTrace	Boolean	false	Enables process trace output.
cli.extractionMode	String	value	Controls what is extracted from each path. See extraction modes below.
cli.delimiterChar	String	|	Delimiter character used in delimited extraction mode.
cli.releaseChar	String	—	Escape character. Required when using delimited mode.
cli.errorOnNullSource	Boolean	false	When true, fails execution if the source document is empty.

Extraction modes (cli.extractionMode):

Value	XML behavior	JSON behavior
value	Extracts node text or value	Extracts property value
entity	Returns the complete XML fragment	Returns the complete JSON object or array
name	Returns the local element name	Not supported
qname	Returns the qualified element name (including namespace prefix)	Not supported
delimited	Flattens all leaf values into a delimited string	Flattens all leaf values into a delimited string

XPath JSON

The XPath JSON is the primary extraction configuration. It defines which fields to extract and which DDPs to publish the results to.

Minimum configuration:

{
  "pathMap": {
    "ddp_customerNumber": "/Order/Header/CustomerNumber",
    "ddp_orderNumber": "/Order/Header/OrderNumber"
  }
}

The pathMap section is required and must contain at least one key-value mapping. Each key is the DDP name to publish; each value is the extraction path.

Source override

By default, Ausa extracts data from the current document in the process. To extract from a DDP instead, specify a source field:

{
  "source": "ddp_semanticXml",
  "pathMap": {
    "ddp_messageType": "/Message/Header/MessageType"
  }
}

Ausa reads the contents of the named DDP and performs extraction against that data source.

XML extraction

Ausa supports namespace-aware XPath processing automatically. No additional namespace configuration is required.

Example:

{
  "pathMap": {
    "ddp_messageClass": "/Invoice/Header/MessageClass",
    "ddp_supplier": "/Invoice/Supplier/Name"
  }
}

JSON extraction

Ausa supports two JSON path syntaxes interchangeably.

Native JSONPath:

{
  "pathMap": {
    "ddp_messageClass": "$['invoice'][0]['messageClass']"
  }
}

Slash path:

{
  "pathMap": {
    "ddp_messageClass": "/invoice[1]/messageClass"
  }
}

Concatenation

Ausa can generate composite DDP values by concatenating multiple extracted values. Concatenation is processed after all extraction operations complete.

Example:

{
  "pathMap": {
    "ddp_firstName": "/person/firstName",
    "ddp_lastName": "/person/lastName"
  },
  "concat": {
    "ddp_fullName": [
      "%ddp_firstName;",
      " ",
      "%ddp_lastName;"
    ]
  }
}

Result: John Smith

Reference extracted DDPs using the %ddp_name; token syntax within the concat array.

Dynamic Document Properties

Ausa publishes the following Dynamic Document Properties (DDPs) during execution, in addition to any user-defined DDPs configured in the pathMap.

Property	Description
ddp_ausa_statusCode	Execution status code. 1 = success, 0 = failure.
ddp_ausa_statusResponse	Execution status text. Values: success or error. Use in downstream decision logic.
ddp_ausa_logJson	Complete execution log including configuration source information, runtime warnings, validation failures, and execution status. Intended for troubleshooting and support.