Can i change settings/jobs etc via XML

I know the location of the XML file.
*\VisualCron\settings\*

Reason:
Want to change this :
And there a lot of jobs which are having this setting.

I dont want to click every single job 🙂

Anyone any tips?

Hi,

I think you can do that. You have to restart the VC service afterwards to let the changes be active.

I do, however, not recommend this. It is easy to make a mistake in the xml file and your job file is currupt. I don't know how Visualcron reacts if that happens.

If you are handy, you can do this with the API I think. You can itterate through all the jobs/tasks and do some changes there. That is a more robust solution.

If you still want to modify the job.xml try the folowing:
Make a backup of your settings, using the standard backup job. It creates a zip file and that contains the job.xml. Make a copy of this zip and alter the job.xml in that copied zip file.
After that you can import settings from that copied zip file and only 'update' the job section from it. If that fails, you still have the original backup file which contains the good job.xml

Good luck!

---

Mucho Gracias

I tried it with the XML file and it worked!

I wanted to do with the API but couldn't figure that one out.

Solved
Copy Job.xml from VC directory
make the change via notepad ++ (i used search and replace because i needed to change time out time and retry's for almost 600+ jobs..)
Stop VC server and service.
Copy the modified version back into the VC directory and then start the server.
JOB DONE

Mucho Gracias

I tried it with the XML file and it worked!

I wanted to do with the API but couldn't figure that one out.

Solved
Copy Job.xml from VC directory
make the change via notepad ++ (i used search and replace because i needed to change time out time and retry's for almost 600+ jobs..)
Stop VC server and service.
Copy the modified version back into the VC directory and then start the server.
JOB DONE

Great! Glad you got it working. It is doable yes, not something we recommend/support really though, to change/modify the xml files, but in your particular case I can understand why you wanted to go that route.