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


Ben Graham
2015-07-11T17:37:17Z
We have a number of jobs that we call from other jobs and pass variables to control specifics of the job execution (target directory, for instance). We just upgraded to 7.7.2 from 7.5 and now, whenever we call a job and pass a variable value it will overwrite the default values with whatever was passed. This is new behavior and has screwed up some of our jobs.

Example:
1. Job A has a job variable called Var1 with a default value of DefaultString.
2. We call Job A using a task of type run job has the job variables set. It passes CustomString as the Var1 value of Job A.
3. After successfully running if we open Job A and look at its variables it still has one called Var1, but Var1 has a default value of CustomString instead of its previous value of DefaultString.

Sponsor
Forum information
Support
2015-07-13T09:59:22Z
There is a setting in the Job/Task Control Task that is called "Update Job Variables". Uncheck this if you want other behavior. I believe that this was there before but did not work as expected.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top