...

Ultra Pipelines are similar to web service requests and conform to an HTTP response architecture. Consider these guidelines when you design an Ultra Pipeline.

Naming

Avoid spaces in Pipeline names that are invoked as Tasks.

Input View Type

An unconnected input view type must be either binary or document:

...

• If the view type is a document: 
  • The output document is JSON-encoded and sent back to the client as the response body.
  • To customize the response header and HTTP response code:
    • Map the response body to the $content field of the output.
    • Map the custom header fields to the root($) in the output.
    • Map the custom HTTP response code to the $status field of the output.
  • The other fields in the output document are treated as HTTP response headers to send back to the client.
  • If a content field is not present, the entire document is JSON-encoded and used as the response body to be sent back to the client.
• If the view type is binary data, the binary file's header is sent back to the client as HTTP response headers. The body of the binary file is directly streamed back to the client.
• SnapLogic expects exactly one output document for every input.
• If the output is not sent, then the original HTTP request sent to the FeedMaster hangs, eventually reaching a timeout.
• If more than one output document is generated, then SnapLogic only sends the first one back as the response to the original HTTP request. This behavior is different from a Triggered Task, where all of the documents sent to the unlinked output are sent back in the response.
• Error views are implicitly added to all Snaps when the Pipeline is executed in Ultra mode, regardless of how the Snaps are configured.

Naming

...

• .

Downloads

...