a job transferring from one flow to another without having a static end/beginning-folder
Posted: Tue Nov 18, 2014 9:35 am
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.
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.