In the help dialog for the Conditional processor, it says if you need more than 8 variables you need to chain the Conditional Processor with 2 or more processors.
I actually just need 9, so what I've done is enter 8 variables all with "Or" and then connect this to another Conditional processor and the first variable is set with a "Then", but this doesn't seem to be working correctly for me, as when I put some media in, one variable from the first conditional processor is positive, so it goes to the next processor checks the standalone variable and comes up negative, so the workflow stops at that point.
So my question is basically, what am I doing wrong with the Conditional chaining in order to use more than 8 variables?
Proper way to chain Conditionals
Proper way to chain Conditionals
FFAStrans 1.2.0
HP DL360p Gen8 - 2x Intel Xeon E5-2670 - 32GB RAM
2x HP SL230s
Windows Server 2008 R2 SP1 64-bit
HP DL360p Gen8 - 2x Intel Xeon E5-2670 - 32GB RAM
2x HP SL230s
Windows Server 2008 R2 SP1 64-bit
Re: Proper way to chain Conditionals
Hello Noqras and welcome here!
Ok here is how I see your problem : If 1 of all (9) conditions is ok then success. That's means if 1 of your first condition node is true then success. So no need to go to the second condition node. If no condition is true in the first node than no success(error) so right click on the second condition node and select "execute on error".
To resume : link your first condition node on success to the next node of your workflow AND link always this first condition node on error to the second condition node. At last, link this second condition node either on success to the next node of the workflow and on error to whatever you want.
I join a workflow to show you . In my workflow, if 1 of all conditions is true, the file will be encode in H264, if no one is true then send an email.
Hope it helps.
Cheers.
Benjamin
Ok here is how I see your problem : If 1 of all (9) conditions is ok then success. That's means if 1 of your first condition node is true then success. So no need to go to the second condition node. If no condition is true in the first node than no success(error) so right click on the second condition node and select "execute on error".
To resume : link your first condition node on success to the next node of your workflow AND link always this first condition node on error to the second condition node. At last, link this second condition node either on success to the next node of the workflow and on error to whatever you want.
I join a workflow to show you . In my workflow, if 1 of all conditions is true, the file will be encode in H264, if no one is true then send an email.
Hope it helps.
Cheers.
Benjamin
- Attachments
-
- Cond.xml
- (4.65 KiB) Downloaded 317 times
Last edited by momocampo on Tue Dec 17, 2019 7:43 am, edited 1 time in total.
Re: Proper way to chain Conditionals
Oh yeah, that totally makes sense. I knew I was missing something basic like that, I was missing the "execute on error" so I wasn't even thinking with that logic.
Thank-you so much for your help!
Thank-you so much for your help!
FFAStrans 1.2.0
HP DL360p Gen8 - 2x Intel Xeon E5-2670 - 32GB RAM
2x HP SL230s
Windows Server 2008 R2 SP1 64-bit
HP DL360p Gen8 - 2x Intel Xeon E5-2670 - 32GB RAM
2x HP SL230s
Windows Server 2008 R2 SP1 64-bit
Re: Proper way to chain Conditionals
You're Welcome
Feel free to come back if you want help.
Cheers.
Benjamin
Feel free to come back if you want help.
Cheers.
Benjamin