...
Field | Field Type | Description | |
---|---|---|---|
Label*
| String | Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline. | |
Content-Type
| String/Expression | Specify the value of the Content-Type header for the binary document. The value of this header is needed to determine whether or not the binary document is, in fact, a multipart stream and what "boundary" is used to separate the parts of the stream. The default value for this property is an expression that fetches the content type from the pipeline parameters (as passed when invoked via a Triggered Task) or the binary input document header. | |
Binary Header Properties | The binary output document header can be modified by specifying properties in this table property. The headers are initially populated with the headers from the parts in the stream. These properties allow you to pass values from the original multipart input document to the binary output documents. | ||
Expression
| Expression | Specify the expression value to insert into the header. When evaluated, this expression, computes the value to insert. | |
Target Path
| String/Suggestion | Specify the JSON path where the value should be set in the header. | |
Snap execution
| Dropdown list | Select one of the following three modes in which the Snap executes:
|
...
Three files are passed from the REST Client. These files are merged and displayed as a multipart output stream.
Snap Pack History
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|