Documentation
  • Introduction
  • Installation
    • Docker Container
      • Database
      • Deployment Modes
      • Docker Environment Variables
      • Deploy on AWS
      • Deploy on Digital Ocean
    • First Steps After Installation
      • Add New Application
      • Publish Application
      • Use Application
  • Usage
    • Send Request To Endpoint
    • Request From Web Form
    • Web Form Controls Having Multiple Values
    • Web Form With File Upload
    • HTML Snippet embedded with Java Script
    • Authentication
    • Environments
    • Debug Mode
  • Configuration
    • Application Directory Structure
      • endpoints.xml
      • security.xml
      • email-sending-configuration.xml
      • service-portal-endpoint-menu-items.xml
      • Directory: data-source-post-processing
      • Directory: data-sources
      • Directory: data-source-xslt
      • Directory: fonts
      • Directory: http-xslt
      • Directory: parameter-xslt
      • Directory: static
      • Directory: transformers
      • Directory: xml-from-application
    • Endpoint Parameter
    • Types of Endpoints
      • Endpoint to Return XSLT Transformation
      • Endpoint to Return Content From Url
      • Endpoint to Return Static File
      • Endpoint to Return OOXML
      • Endpoint to Redirect Request
      • Forwarding Between Endpoints
      • Conditional Success Action
      • Error Case
    • Data Source Transformation
      • Load Parameter Values as a Data Source
      • Load Data From a Local XML File
      • Load Data from any REST-API
      • Load Data From Databases
      • List AWS S3 keys
      • Load AWS S3 object
      • Additional Useful Data Source Types
      • Transformation Options
      • Data Source Post-Processing
      • Using Parameter Placeholders in Data Sources
      • On-Demand Incrementing Number
      • Writing Transformation Input/Output to AWS S3
    • Parameter Transformation
      • Parameter Transformation Input
      • Parameter Transformation Output
    • Tasks
      • HttpRequest Task
      • Email Task
      • Create Shortlink Task
      • Request Log Task
      • Conditional Tasks
      • Parallel or Subsequent Execution of Tasks
      • Intermediate Values
    • PDF Created With XSLT
      • Embedding Fonts
      • Embedding Images
    • OpenEndpoints XSLT Specifics
Powered by GitBook
On this page
  • Literal XML
  • Application Introspection
  • On-Demand Incrementing Number
Export as PDF
  1. Configuration
  2. Data Source Transformation

Additional Useful Data Source Types

Literal XML

The data-source command <literal-xml> lets you define xml output directly and "literally" in the data-source definition file.

<!-- Data source definition -->
<data-source>
    <literal-xml>
        <any-tag/>
    </literal-xml>
</data-source>

The root tag <literal-xml> is not included in the data-source xml output. In the example above, the generated xml will be:

<!-- Generated XML -->
<transformation-input>
    <any-tag/>
</transformation-input>

This data-source-type can be perfectly used in combination with parameter placeholders. For example, you can use something like this:

<!-- Data source definition -->
<data-source>
    <literal-xml>
        <any-tag>${foo}</any-tag>
    </literal-xml>
</data-source>

If ${foo} equals "hello world", the data-source output will be:

<!-- Generated XML -->
<transformation-input>
    <any-tag>hello world</any-tag>
</transformation-input>

Note that the contents of must be elements, simply placing text straight under the <literal.xml> element will not work.

Application Introspection

This content-source produces as its output a description of the entire application directory structure (=your configuration).

The generated content has a root-tag <application-introspection> and returns

  • <directory name="x"> for any directory

  • <file name="x"/> for all XML files. The content of the XML file is included as a child of this tag, except the directory xml-from-application. (Use the <xml-from-application> data source, not <application-introspection> to load content from such files.)

  • <file name="x"/> for all non-XML files. In this case the content is not in any way included.

XML files must actually contain XML

If a file named *.xml does not in fact contain well-formed XML, this is an error.

No expansion of endpoint parameters

Parameters like ${foo} found in the file are not expanded in this type of content-source.

On-Demand Incrementing Number

PreviousLoad AWS S3 objectNextTransformation Options

Last updated 1 year ago

<OpenEndpoints/> can generate unique auto-increment values and provide them as a data-source. Read for more details.

On-Demand Incrementing Number