All,

I am using conditions to handle some basic looping/polling.

task 1 - ftp download a file
task 2 - if {TASK(PrevTask,Result.NoDownloadedFiles)} = 0, goto task 1

Works great, but I need this condition in many places so I don't want to have to "hard code" Task 1 in the goto logic. If I have to hard code the task to be executed based on task name/id, then I will need a unique condition set for each occurrence.

Any thoughts on how to make this condition/logic generic and reusable?

Regards,

Chuck

So basically you would like us to add an option to specify "Previous Task" or "Current Job"?

---

That would work, in the case where it is truly the previous task (most frequent occurence currently).

Another thought is to allow the use of a variable that indicates the task ID in question and the job would have to assign the appropriate task ID to the variable prioir to evaluation of the condition. Although that could present problems since the conditions have a global scope.

Thanks,

Chuck

Ok, thanks for the input. Moving topic to Feature requests.

---