Skip to content

Data formats

Four boxes, all built on the same model: a parse or stringify operation, a value input, a result output.

Inputsvalue
Outputsresult
Configurationop: parse or stringify; indent (0 = compact, 10 at most)
Inputsvalue
Outputsresult
Configurationop, indent (10 at most)

Attributes are exposed under the @_ prefix in the object produced: <client id="42"/> yields { client: { '@_id': '42' } }.

That is what you need in order to work with a SOAP response as something other than plain text.

Inputsvalue
Outputsresult
Configurationop, indent (1 to 10, default 2)
Inputsvalue, delimiter (string)
Outputsresult
Configurationop, delimiter (default ,), header (default true)

With header enabled, parse produces a list of objects named after the first row. Combined with Read file and ForEach, that is the data-driven test pattern:

Lire fichier « jeux.csv » ──► CSV (parse) ──► ForEach
└─ each ──► Requête HTTP