In my case, I have a job that has restrictions before it can run to completion.
The first few tasks are my conditions, in this case, I issue a SQL query to see if the current day matches a holiday entry in our holiday table. If it does, I don't want the job to run. Otherwise, I want it to continue to the next step. How would I set up a condition that checks the holiday SQL task and only continue to the next step if the output is ""?

In my case, I have a job that has restrictions before it can run to completion.
The first few tasks are my conditions, in this case, I issue a SQL query to see if the current day matches a holiday entry in our holiday table. If it does, I don't want the job to run. Otherwise, I want it to continue to the next step. How would I set up a condition that checks the holiday SQL task and only continue to the next step if the output is ""?

You can use 2 type of Conditions here. Either the VisualCron condition which can check the output or the Variables Condition which can compare two Variables (like the std output variable and your value) - it is up to you.

You create this Condition and check it on the Task that follows the SQL Task. You can control if it should run the following Task either by editing Actions of the Condition or altering the operators of the Condition (is not, not contains etc).

---

My question is, how do I set up the condition to test for nothing? My options under task are:
Exit code {is,is not}
Output {is,is not,contains}
is running

I am using the "Output" check, but don't know whether to use two quotes: "", nothing or blank on the input box to indicate a nothing return on the previous task.

If the SQL Task returns nothing the output will be "" so, you can just leave the field in the VisualCron Condition empty.

---

That's the thing. I've tried using VisualCron Condition and set it to empty. It asks me if I"m sure I want to set it to empty before saving and I say yes. Task still runs even though the previous task output is not "".

The Condition I'm setting is visualCron.
Under 'task:' I'm selecting output, then 'is' in the pull-down and leaving intput blank.

The task is still firing off.

If you do not want it to fire of you should use "Is not".

---

That doesn't make sense. The firing should be based on whether a condition is met or not met.
For instance, if I have a condition that calls for firing off a task when the previous task's output is "DONE", I should be able to set a positive condition like the output of the previous step is "PEND" or a negative condition such as the output of the previous step 'is not' "DONE".
Are you saying the "Is not' condition being met is the only one that will keep a task from firing?

How does one attach screen prints?
I would like to show you screen prints of the results I'm getting when I set and execute tasks with conditions.

That doesn't make sense. The firing should be based on whether a condition is met or not met.
For instance, if I have a condition that calls for firing off a task when the previous task's output is "DONE", I should be able to set a positive condition like the output of the previous step is "PEND" or a negative condition such as the output of the previous step 'is not' "DONE".
Are you saying the "Is not' condition being met is the only one that will keep a task from firing?

I think there was a misunderstanding. I thought you wanted the following scenario:

Run second Task if first Task output is not empty/nothing.

Now, by default if you set Output Is "" then the Condition will be met and the second Task will run. This is not desired right?

And you can alter this in two ways:

1. Set "Is not"
2. Change the Action of the Task to tell it to NOT continue if output Is ""

You can also add debugging about by check "debugging" in the Condition. Then you will see when, why and what the Condition found and which action it took.

You can attach images by checking "Attach files to this post?" when writing a post.

---

Thank you for your patience Henrik. I didn't realize there was an 'actions' tab to set the action that resulted from the condition. I assumed the condition was the only thing that controlled it.

Your product is very robust. It has met all our shop's needs to this point and thrown in alot of extra features that have made things alot easier for us.

Thanks for the feedback!

---