Final Mapper response is generating [] to it

[Abhishek_Soni37]

Hi All,

I’m stuck with this small problem where I’m trying to send the response(received from Rest Post Snap) via mapper after extracting the required tags form the response but the final Mapper output is coming with hence the receiver system is not able to parse the message as it’s expecting the message in {}.
Expected response format :
{
“IsSuccess”:true,
“Error”:“”
}

Pipeline Response:
[ {
“IsSuccess”:true,
“Error”:“”
}]

Error at the receiver system:
{“Status”:2,“Error”:“Unable to parse JSON: [\n {"IsSuccess":true,"Error":""}\n]\n”}

Is there a way to avoid those before from the response generated by the Mapper?

Pipeline Details:
Main - Rest Post
Type - Triggered task pipeline

Thanks in advance.!

Cheers,
Abhishek

[igormicev]

Hi @Soni37

You should check what you have as inputs in your Gate. Note that you’ll always have input0 and input1. input0 is your Error output from the Post.
Also, it depends on how you handled it in the Mapper.

/Igor

[Abhishek_Soni37]

Hi @igormicev,

Thanks for your input.

But based on the Gate output I’m extracting Whether the http code is 200/500 via mapper.
Even when the Output doc contains only one tag-“http_code” final output is coming with square bracket.

Please find below Snips of the mapper and response:

Thanks,
Abhishek Soni

[del]

@Soni37,

Per the referenced post below:
Add to your existing pipeline a mapper, change its output to binary, and configure the Transformation section like this:

Reference:

Triggered Task respond with plain unformed text (not JSON) Designing Pipelines

You need to have an unlinked binary output view. With the latest release (4.17) you can change a Mapper’s output view to be binary and then write the string you want to $content. Would probably also be wise to set $['content-type'] to text/plain. [image] Here’s how you change the output view through the ‘Views’ tab in the Mapper settings: [mapper-binary-view] I’m attaching a pipeline that demonstrates this: PlainTriggered_2019_06_04.slp (2.4 KB) (If you haven’t upgraded yet, you can use…

[Abhishek_Soni37]

Thanks @del

It worked like a charm. 🙂

Thanks,
Abhishek