In a recent chat about workflows, it was observed that chaining transformations together might be helpful.
This is possible by running Transformation Jobs back-to-back, but requires a) selecting the input job each time, b) selecting the Transformation Scenario each time. It would be handy to do something like,
select an input job
apply n Transformations in order, for each, using the previous job as an input job
One consideration would be validations and the validity valve applied to each stage. Should the same validations get run for each link in the chain? Or have whatever validation scenarios were selected run at the end?
What about record validity? Should there be one selection done at the beginning that applies to all? Or should they be arranged in order?
This issue / enhancement could be generalized to just chaining jobs. It feels like mostly a UI question, with the ability to do this already established in normal workflows.
In a recent chat about workflows, it was observed that chaining transformations together might be helpful.
This is possible by running Transformation Jobs back-to-back, but requires a) selecting the input job each time, b) selecting the Transformation Scenario each time. It would be handy to do something like,
One consideration would be validations and the validity valve applied to each stage. Should the same validations get run for each link in the chain? Or have whatever validation scenarios were selected run at the end?
What about record validity? Should there be one selection done at the beginning that applies to all? Or should they be arranged in order?