Forum Discussion
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?
- cjhoward185 years agoEmployee
This expression in a Mapper snap:
$Items.Item.map(value => value.mapKeys((value, key) => "WM_" + key))
will add the ‘WM_’ prefix to the keys for each item in this Item list.
Having it mapped to the target
Items.Item
will replace the old value with your desired output. - SpiroTaleski5 years agoValued Contributor
Hi @sjakathi
Please check the attached sample pipeline:
SL_Community_2021_02_02.slp (3.6 KB)
Hope this will help.
Regards,
Spiro Taleski
Related Content
- 2 years ago
- 3 years ago
- 4 years ago