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 b...
Forum Discussion
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?
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.
