Ryan F.

Hi Kate S., the context for this question was that during a recent screening, a person was entirely unfamiliar with the new UI. This seemed impossible to me for anyone who actively uses the platform, and I wanted to get some context about timeline of the new UI rollout.

So the "classic" UI stopped being the default in the April release?

I am sharing my observations so any future human or non-human consumers of this information will know how it was resolved.

I added a Mapper Snap where I mapped $ to $content. When I put this before the original Mapper Snap in the pipeline, I get the expected response.

I created a pipeline for an Ultra task with a single Mapper Snap in it. The Mapper Snap had "Pass Through" checked. The mapping table had a static value of 200 for the output of $status. When invoking the task, I get a null response. Based on the above, I would have expected a document containing the incoming headers.

None of the above examples captures my use case. I have a pipeline in use in an Ultra task. I am invoking this Ultra task from outside of SnapLogic (let's say through Postman). I want the pipeline in SnapLogic to be able to be configured to output all headers sent from the external client to the FeedMaster of the Ultra task.

I want to extract all headers present in a request for debugging.

We use pipeline parameters today to capture the task name. I have also submitted enhancement request IIC-I-1533 to add a task.name property that can be used in a Mapper Snap. Supposedly, this enhancement request is intended to be delivered in an upcoming release.