AnsweredAssumed Answered

How to graphically represent dependencies in jobs/trasnformations?

Question asked by Virgilio Pierini on Mar 15, 2018
Latest reply on Mar 22, 2018 by Virgilio Pierini

Hi Community!

My question is in the middle between impact analysis and reverse engineering: I have a solution and I want to be able to connects dependent objects to their callers. I'm not interested in deep detail, not about single columns, not about origin steps for fields. I just need a sort of graph to answer questions like: who calls this ktr? What will stop if this job fails?

Is there any facility in PDI about this? I read about data lineage but -as said- it provides too much information (eg: the information level I need is more stable during development because changes into KTRs are more frequent than NEW KTRs creation).

A home made approach would be to extract dependent KTRs and JOBs from xml source files but I do not want to reinvent the wheel...

Any suggestion on your side?


My regards