Jinja Only Action
Brandon Martinez
Sometimes I have a set of Jinja I need to run on its own to filter or re-organize results. Currently handling this in a transition by creating a data alias but might be a bit cleaner to have a task specifically to execute Jinja. For example, we receive a list of contacts from CWM that has "firstName" and "lastName" objects separate and we need to concatenate them together. Having a workflow action for "Run Jinja" to take those two lists and concatenate them together as its own task would be useful
Log In
Greg Vinyard
I think standard practice is to add a "noop" task, give it a meaningful name and then put this kind of Jinja code in a Custom Condition, but that feels a little hacky. Having a task called out specifically for Jinja code would be nice.