Forum Discussion
Hi @spinaka,
Here is a link of the documentation of how you can get headers.
https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/986383617/Passing+Pipeline+Arguments+to+Triggered+Tasks#:~:text=PATH_INFO%3D%20newvariable1/newvariable2 -,Request%20Pipeline%20Arguments,-You%20can%20pass
You need to put the name of the header in parameters but everything need to be in upper case and spaces to be replaced with underscores as they are shown in the site.
Regards,
Viktor
This is also helpful in one way but have to make little changes at the client end. I tried pipe.args suggested by @bojanvelevski and that is straight forward to capture all. Anyway, thank you much for responding @viktor_n.
Welcome to the Community AnilD!
My standard advice for developers new to SnapLogic is to look at rewriting your Python code using standard SnapLogic snaps. It's a good learning experience to learn how to effectively use the platform and you have much more supportable code in the long term.
I assume that the thought process is that you have your scripts that work in Python and the Script snap supports Python, so "why not just plug it in and move on?"; unfortunately, the Script snap has a specific ScriptHook interface that must be implemented to execute within a SnapLogic pipeline, doesn't offer highly robust error messaging, and has specific external library implementations that may not be supported by your server admins.
If you want to continue using your Python scripts as-is, my recommendation is to use your enterprise scheduling tool to run the Python scripts directly (outside SnapLogic) and implement your other app/data integrations in SnapLogic.