Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


hansvl
2020-10-09T08:57:13Z
In tasks I use {JOB(Active,Variable,LOGFILE)}.
What is he right name, JOB function?
Where can I find documentation about the use, behavior and the three parameters?
Sponsor
Forum information
Casper
2020-10-09T21:06:37Z
Originally Posted by: hansvl 

In tasks I use {JOB(Active,Variable,LOGFILE)}.
What is he right name, JOB function?
Where can I find documentation about the use, behavior and the three parameters?



Hi hansvl, I think you can use like that: {JOB(Active|Variable|LOGFILE)}

More documentation about variables:
https://www.visualcron.com/documentation.aspx 
hansvl
2020-10-13T08:42:04Z
Hi Casper,

Thank for your reaction.
But to be honest, this doesn't make me any wiser.
I wonder what the first argument "Active" means and whether another first argument is possible.
In the documentation I cannot find that information.
thomas
2020-10-13T08:58:33Z
If you open the variables windows you will see the meaning:

image.png

Active will be the running job, ie it is determined at runtime. If you want to point to a job variable in a different job, you can use direct id

image.png

Generally speaking I would avoid using direct id as much as possible. This is my preference, not a rule.

Thomas
Joey S
2020-10-15T19:44:04Z
Quote:

Generally speaking I would avoid using direct id as much as possible. This is my preference, not a rule.

Thomas



I agree. If/when you clone that job to another you do not want the GUID for Job A to be anywhere inside of Job B. That creates a lot of confusion.

The "Active" and "Prev" (previous) variables are very helpful.

The only problem you may find is trying to troubleshoot without the job running or being inside of the job/tasks..."Active" is meaningless if you are not using that job. "Available at runtime" is my nemesis.
Users browsing this topic
Scroll to Top