Hi,
We have a triggered pipeline that returns JSON.
Here is the example of the output:
[
{“metadata”:{“version”:“1”},“content”:[{“elementType”:“detail”,“title”:“Gleb”,“content”:}]}
]
The problem is that brackets are causing the issue for the vendor that calls this pipeline.
How do we remove brackets?
Here is the desired output:
{“metadata”:{“version”:“1”},“content”:[{“elementType”:“detail”,“title”:“Gleb”,“content”:}]}
Thank you,
Gleb.
@Siva_Venna No Siva, the pipeline param are static and final, can’t change or can’t assign as target value in mapper.
thank you @Supratim
my pipeline exposed as triggered task and it has to accept different files and write to destination location. is there a solution to pass file name dynamically based on input file content(files will contain attribute that define file name)?
@Siva_Venna You can declare the pipeline parameter and pass the value for it from the calling environment of your trigger task, then you can refer the same parameter reference in the pipeline to create the file.
Please see the below screenshot:
Refer the below documentation link for more information on how to pass the pipeline properties as query params for a trigger task.
https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/986383617/Passing+Pipeline+Arguments+to+Triggered+Tasks
Also you don’t have to parse and then format the file content instead you can even write directly to the file using FileWriter snap.
@Siva_Venna you can also pass the pipeline parameter as a custom header:
Please refer : https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/986383617/Passing+Pipeline+Arguments+to+Triggered+Tasks
Or else you can pass it as value with in the XML and retrieve the same information using mapper and write the remaining content to the file.
