Idea ID 1641481
Much like filters on step outputs, I would like to be able to set filters on inputs
Because OO is primarily an integration system, I find myself using it to pass data back-and-forth between various service providers to make decisions, etc. Sometimes, different providers want the data in slightly different formats which means I do a fair amount of data transformation in Do Nothing steps before passing the data to teh service providers.
This equates to: "Do Nothing" step, create the corresponding outputs, apply the relevant filters, and then those modified outputs are used by that one provider (but nothing else).
Having filters on inputs would reduce flow complexity and improve efficiency (because you are cutting steps out of flows, which is always a good thing).
- Filters are executed before the "Assign to Variable" phase of the operation (so that the new assignment variable picks up the filtered value
- Are executed before the scrtpts are run (so in Nashorn, the input variables are created with the filtered value)
Aside: I'm not sure about the value of having the "Assign to Variable" section on inputs. IMHO, you have the ability to create context variables by creating an output (based on the value of an input). Creating them directly from inputs actually makes flows more difficult to debug/learn because it means you have to look in two places to find out where a particular context variable has been set. It makes flow development more confusing (IMHO).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.