Pipeline Execution Label in Tasks

When a task invokes a pipeline, the pipeline name appears in the dashboard. Given the parameters they accept and pass into pipelines, the tasks and pipelines can be very dynamic in nature. It would be very helpful to see a label in the dashboard to identify which objects that tasks and pipelines were operating on, given that the pipeline name would be the same for a multitude of objects. I know this enhancement request has been around for quite a long time, but I’m adding it here to keep it fresh. Apparently it’s not high on SnapLogic’s priority, but it would be an extremely helpful feature in an upcoming release.

Hello,

Are you referring to triggered tasks? This is a great suggestion, but I’m curious if you have any specific ideas about how you’d want to configure the task so that the label includes the information you care about.

Thanks,
Patrick

I imagine it like something that is akin to how the pipeline execute task works. With the pipeline execution, there is an expression that can be used for the pipeline’s label. The label value is what gets presented on the dashboard. The same type of thing could be set up between the task and the pipeline that it is invoking. The pipeline’s edit configuration could contain a place where an expression could be entered and that expression could accept values that are passed to it from the task that is invoking it.

I hope that makes sense. Let me know. I could try to draw a some illustrations.

Yes, it does, thanks. That’s basically what I thought you meant. But this is a bit of a different problem than for Pipe Exec, which evaluates the expression to set the child pipeline’s label for each input document in the context of the parent pipeline, before the child pipeline starts. With a triggered task, it raises some questions. A triggered task only executes a single pipeline per request, and if the request contains an array, the first snap will receive each element as a separate document. So the question is how to evaluate the expression used to set the pipeline’s label before the pipeline is running, and what exactly should it be evaluated against? Just pipeline parameters (which includes the request metadata)? Or also documents? Just the first document if there’s more than one? Or the array before it’s split into multiple documents?

1 Like

Something like this is what I was imagining, where a execution label expression could be added to the pipeline’s parameters. This could either go here on on the task. Might be better on the task.

1 Like