Skip to main content
Feedback

Grenefolc Vartala Ausa — Partner connector

The Grenefolc Vartala Ausa - Partner connector is a configuration-driven XML and JSON data extraction connector for Boomi. It operates entirely locally and makes no external network calls or connections.

Ausa extracts data from XML and JSON documents using configurable extraction paths and publishes the results as Dynamic Document Properties (DDPs) for downstream process execution. It is designed to provide lightweight metadata extraction and enrichment without requiring full document profiling.

The connector supports:

  • XML XPath extraction
  • JSON Path extraction
  • Shared slash-path extraction
  • Entity extraction
  • Element name extraction
  • Delimited flattening of complex structures
  • Composite property generation through concatenation
  • Alternate extraction sources via Dynamic Document Properties

Connector configuration

To configure the Ausa connector, set up the following components:

  • Ausa connection
  • Ausa operation

This setup creates reusable components that separate connection settings from operation settings.

After configuring both components, place the Ausa connector into a process. Ausa then extracts the configured fields from each inbound document and publishes the values as DDPs for downstream use. The connection object contains no configuration and exists only to satisfy Boomi connector requirements.

Business use cases

  • Routing metadata extraction — Extract key fields (message type, sender, receiver, order number) from XML or JSON documents and publish them as DDPs to drive downstream routing decisions without transforming the full document.
  • Composite value generation — Concatenate multiple extracted fields (for example, first name + last name, or sender ID + message type) into a single DDP for use in process routing, logging, or cache key generation.
  • DDP-sourced extraction — Extract data from a DDP containing XML or JSON (such as a routing profile generated by the Stefna connector) rather than the current document, enabling multi-stage enrichment pipelines.

Limitations

  • Ausa does not perform full document transformation or field mapping. It extracts metadata only.
  • The name and qname extraction modes are supported for XML only; they are not supported for JSON.

Tracked properties

This connector has no predefined tracked fields. Use the Dynamic Document Properties published by Ausa (ddp_ausa_statusCode, ddp_ausa_statusResponse, ddp_ausa_logJson) and any user-defined DDPs configured in the pathMap in downstream process steps.

On this Page