Subject:Archiving output from conversion Author:Bruce Cantor Date:25 Jan 2022 12:26 PM
I was wondering if there might be a better solution to this challenge that I often have:
We often convert our internal XML files to other XML file formats.
We would like to keep a copy of the output in an archive folder, making it easier to troubleshoot problematic files later.
A typical simple pipeline would then consist of a pipeline input node, a xslt node and the two pipeline output nodes.
I have noticed that forking output from a xslt node to a output node is troublesome.
I am not sure about the behaviour, but usually one ore both output nodes ends up not getting output.
It can be solved by adding a xslt node that does nothing else than copy the previous document output and the take archive and output from the two different nodes. This works, but then a redundant xslt script is added to the transformation.
I found that if I use a XML parser node in SS the output is parsed correctly to both nodes, but not sure if this is more or less ressource demanding. Or if it works in Pipeline server.
Attached is a visual representation of the question, the different scenaries represented by each input node.