Multipart Request Generator - Data360_Analyze - 3 - 3.12

Data360 Analyze Server Help

Product type
Software
Portfolio
Verify
Product family
Data360
Product
Data360 Analyze
Version
3.12
Language
English
Product name
Data360 Analyze
Title
Data360 Analyze Server Help
Copyright
2023
First publish date
2016

Enables you to prepare a valid multi-part body, which can then be passed to the HTTP node for processing.

The HTTP node uses its from Field variant of the Body property to get the appropriate multi-part body.

Properties

BodyField

Specify the field name in the input data, which contains the values that will make up the content of the generated multipart body output.

The field on the output pin which will contain the generated multipart body will be as specified in the MultipartBodyOutputField property.

A value is required for this property.

BodyInputMode

Optionally specify whether the values coming from the input field as specified in the BodyField property should represent a field or file in the generated multipart body. Choose from:

  • Field
  • File

Use the From Field variant of this property to look up the value from an input field with the name specified.

The default value is Field.

ContentType

Optionally specify the content type for the value identified in the BodyField property.

Use the From Field variant of this property to look up the value from an input field with the name specified.

Headers

Optionally specify the headers for the current part of the multipart request.

Headers must be in the form of <header name>:<header value><seperator><header name>:<header value> where the <separator> used should match the one that is specified in the HeaderSeparator property.

Use the From Field variant of this property to look up the value from an input field with the name specified.

HeaderSeparator

Optionally specify the separator that will be used to separate header entries in the Headers property.

The default separator is ",".

MultipartRequestIdField

If there are multiple parts to be built into a single multipart body (where each input record is a separate part), optionally specify the name of the input field that groups the parts together, to form a single multipart request body.

ControlName

Specify the control name of the current part of the multipart request.

Use the From Field variant of this property to look up the value from an input field with the name specified.

A value is required for this property.

MultipartBodyOutputField

Specify the name of the output field that will contain the generated multipart request body.

A value is required for this property.

ContentTypeOutputField

Optionally specify the name of the output field that will contain the content type for the generated multipart request body.

MultipartCharset

Optionally specify the character set of the generated multipart request body. Choose from:

  • ISO-8859-1
  • US-ASCII
  • UTF-8
  • UTF-16

MultipartMode

Optionally specify the mode used to generate the multipart request body. Choose from:

  • Strict: RFC 822, RFC 2045, RFC 2046 compliant.
  • Browser Compatible: only write Content-Disposition. Use the content charset.
  • RFC6532

The default is Strict.

PassThroughFields

Optionally specify which input fields will pass through the node unchanged from the input to the output (assuming that the input exists).

The input fields specified will appear on those output records that were produced as a result of the input fields. Choose from:

  • All - Passes through all the input data fields to the output.
  • None - Passes none of the input data fields to the output. As such, only the fields created by the node appear on the output.
  • Used - Passes through all the fields that the node used to create the output. Used fields include any input field referenced by a property, be it explicitly (meaning through a 'field1' reference) or through a field pattern (meaning '1:foo*').
  • Unused - Passes through all the fields that the node did not use to create the output.

The default value is Used.

If a naming conflict exists between a pass-through field and an explicitly named output field, an error will occur.

SortInput

Optionally specify whether the input will be sorted, based on the field specified in the MultipartRequestIdField property.

The default is True, when the MultipartRequestIdField property is set, otherwise it is False.

Enabled

Optionally specify whether the node is enabled or disabled. You can choose either True or False, or reference another property (see Using derived property values) which will be evaluated to a True or False value.

Disabled nodes are not executed, even if they are selected to run.

The default value is True.

Note: The Enabled property cannot reference any of the Run Properties of a data flow, either directly or indirectly.

Inputs and outputs

Inputs: 1 (in1).

Outputs: 1 (out1).