Visokio website     Downloads     Video tutorials     KnowledgeBase  
Scheduler: event-driven automation via watchfolder? - Visokio Forums
Scheduler: event-driven automation via watchfolder?
  •     davedunckley February 6, 2013 10:13AM
    Hi Guys - I would like my Omniscope IOK file to run not from on a time schedule, but from a file drop. I have found the 'wait for file' command, but can't work out how I make this a chain reaction?

    Any help would be great.- Dave
  • 5 Comments
  •     tjbate February 6, 2013 11:06AM
    Dave- You can take control of Scheduler and submit Task Lists by writing an XML Actions file (re-writtten by your system from the configured model copy XML file exportable from the Scheduler) to the nominated watchfolder specified in the Scheduler.

    Every time you write an XML Actions file to the watchfolder (i.e. event-driven rather than time-driven), the Scheduler will immediately execute the chain of tasks, then delete the XML Actions file and wait for the next one.

    For more detail, see:
    http://forums.visokio.com/discussion/1982/scheduler-running-from-a-3rd-party-applications

    http://forums.visokio.com/discussion/1231/scheduler-setting-task-time-outss

    http://forums.visokio.com/discussion/826/scheduler-execute-command-action
  •     davedunckley February 6, 2013 11:12AM
    And how do I go about making an action file?
  •     tjbate February 6, 2013 11:15AM
    See the model XML Actions files at the bottom of this link:

    http://forums.visokio.com/discussion/1982/scheduler-running-from-a-3rd-party-applications
  •     davedunckley February 11, 2013 6:54AM
    Sorry but I have no idea what this all means. I would very much like to be able to open, update, and save. All triggered by a file being droped.

    Is this possible, if so how?

    Thanks

    Dave
  •     tjbate February 11, 2013 7:29AM
    In the Scheduler, you specified a folder to be the 'watchfolder'. You can 'record' a sequence of file actions such as open, update and save file actions using the Scheduler, then export the 'recorded' script as an XML Actions text file. Every time your own system copies this XML Actions file (or a valid, modified version) into the watchfolder location, the Scheduler immediately executes the file actions specified in the XML Actions file, then deletes the copy of the XML Actions file in the watchfolder and waits for the next XML Actions file to be copied into the watchfolder by your own system.

Welcome!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership