a job transferring from one flow to another without having a static end/beginning-folder

[mfeldmann]

Hi there,



I have quite big flow, were I try to do a lot of different things. If I have problems with one part of the flow, I need to stop everything. Now my idea is to split this one flow into some flows, that work a kind of separate.

For example (very simple):

The first flow only sorts job by customer A, and customer B. At the end of the first flow is a OUT-A folder and OUT-B folder.

In a second and third flow, for each customer one, starts the further process with the OUT-A and OUT-B folder of the first flow.

Is there a way to not have that OUT-A or OUT-B managed as a static folder, so that switch managed this folder internal only?



Thanks in advance for your input and help.

[freddyp]

Use "Archive hierarchy" at the end of the first flow. That will give you different output folders, but only one fixed root folder.



In the other flows you will have to point to the specific folder. You could also use "Submit hierarchy", but then you would still have to use a rule to limit the processing to just the folder that you need for that flow. And that defeats the purpose.



Use "Strip unique name - No" to keep all the metadata of the job in the second flow.



Freddy

[nicktazo]

My way is exporting xml+pdf at end of the 1st flow, and pickup them at the begin of the 2nd flow.



Nick