Is there no concept of private variable in a job?

When i clone a job I must go through and update all the tasks that reference other tasks within the job.

If I set the output of a task to a global variable, but the two jobs run at the same time, things conflict.

Maybe I'm missing something?

Thanks,

Drew

Yes, the idea is that it is global. If you want to make unique right now you have to add some unique value like Job id in Variable.

---

Yes, if i did that for a single job, for my 35 customers, and the job had 5 variables, I'd have 175 variables I'd have to create today.

Even if I could reference a task by a name, say we call the task that gets the POSIX time "PosixTime" then instead of referencing by GUID, or "Previous Task" (which is only useful for the task following the Posix time task, not any subsequent tasks) when I cloned the job, you would not have to update all these references.

Drew

Yes, the idea is that it is global. If you want to make unique right now you have to add some unique value like Job id in Variable.

I understand. I am moving this to Feature requests.

---

I understand. I am moving this to Feature requests.

Henrik, I did think over what you said for some time, and ended up using a set variable command which includes the JobID in the variable name.

This solves my problem, in that when i clone a job, the variables will reference the new jobs GUID.

It still will result in my having, many hundreds of variables. Also, I realized that if I remove a job, I'll have to go in and manually find and delete all the variables with the GUID of the job deleted.

Thank you for your consideration.

Drew

Job Variables was implemented a while ago.

---