Forum Discussion

Szymon's avatar
Szymon
New Contributor II
4 years ago
Solved

Binary output - error pipeline - custom http codes

There is a requirement for the following: Error pipeline for an ultra pipeline which responses with custom HTTP code, e.g. 500. Why: …The third party API caller shall receive a proper HTTP code...
  • Aleksandar_A's avatar
    Aleksandar_A
    3 years ago

    Hi @ash42,

    Do you want the output to be only one object?

    If yes, then try with the following expression in a Mapper Snap:

    $Names.reduce((acc,curr,ind) => acc.extend({[curr]: $Values[ind]}), {})

    The output will look like this:

    [
	{
		"key1": "Value1",
		"key2": "Value2",
		"key3": "Value3"
	}
]

    Let me know if this is the desired output.

    BR,
    Aleksandar.

j_angelevski's avatar
j_angelevski
Contributor III
4 years ago
Copy LinkReport

Hi @Szymon,

  1. is it not possible to have a binary output in ultra? YES or NO

Yes, the ultra pipeline should have at least one open output view and one input view. If you use an error pipeline with the ultra pipeline, the error pipeline must have an open output view.

  1. what is the alternative to output custom error codes from error pipeline, so the calling party sees, not HTTP 200, but HTTP 500? I DO NOT WANT to use Error View at the particular snaps in Ultra pipeline!

To output a custom status code, you can pass the $status header to the output snap ( for example JSON Formatter in the Binary header properties ) with your desired value. You can also do the same in a Mapper snap with binary output view if you want custom status code.

Szymon's avatar
Szymon
New Contributor II
4 years ago
Copy LinkReport

Thank you,
I am sorry, I was not making it 2000% clear, so updated the initial post for that.

ad 1. Now, the error, that I get is referring to the error pipline, that is used in ultra.
So, is it not possible to use binary output view in the error pipeline?

ad2. The goal is not to output custom http codes from the ultra pipeline itself, BUT from the error pipeline. When in error pipeline I do - as you suggest - convert document to binary using $status and $content, the error mentioned occurs, as soon as engine initializes the ultra pipeline.

  • Aleksandar_A's avatar
    Aleksandar_A
    Contributor III
    2 years ago
    Copy LinkReport

    You can try with enabling the expression evaluation, and with the following expression:

     

    "SELECT ConversionRate, CreatedById, CreatedDate, Id, IsoCode, LastModifiedById, LastModifiedDate, NextStartDate, StartDate, SystemModstamp FROM DatedConversionRate 
where IsoCode in("+$currencyCodes+")"