You can design your Pipelines to act like REST APIs. You can run Triggered Tasks using the following HTTP Methods from both Cloudplex and Groundplex instances:
Triggered Tasks support viewing the output of a Pipeline. When you execute a Pipeline using a Triggered Task URL, the output can be included as response to the HTTP request. You can create a Pipeline to be used in this manner by leaving one output view unconnected. For example, a Pipeline that consists of only a File Reader Snap would return the contents of the file when the Task URL is requested.
This feature works with both document and binary views.
status
and its value an HTTP response status code, as shown below:
Pipeline Design for POST Requests
You can POST input to a Pipeline. If you send a document to a Pipeline, you can leave one input view unlinked and then do an HTTP POST call to the Task URL. The content of the POST request is then turned into a document and fed into the Pipeline.
Consider the following options:
If the input view accepts documents, then the content of the POST request should be a JSON-encoded object or an array of objects.
|