Job properties

This window contains selected job-specific properties.

Variable list

Here you can manage the variables, used by tasks

If job tasks tasks using variables, all task variables listed here. You can assign variable values facilely. Here you can’t rename or delete variable (variable refactor implementation in progress), if you want to remove variable, simply remove it from referenced tasks.

Task list

There is the job’s task list. One job can contain multiple tasks. The execution order of tasks within one job is identical to the order of listed items.

  1. Enable / Disable current Job. The tooltip of the “Name” field shows the XML name of the saved job file.
  2. Job name
  3. Job description
  4. The log level:
      • SERVE: log only critical errors
      • WARNING: log critical errors, and warnings
      • INFO: log messages, critical errors, and warnings
      • FINE: log everything (Attention: this generates in some cases a lot of log data! Use it for job debugging purposes only.)
  5. List of job contained tasks
  6. Enable / Disable selected task
  7. Add task
  8. Edit task – Open selected task properties (Task properties)
  9. Delete task
  10. Save job – Save modifications, close this dialog
  11. Cancel job – Cancel modifications, close this dialog

TIPP: you can drop files to tasklist (6), and task(s) with simple filter created automaticly (ver 0.63)

If variables defined, Variables tab contains Job specific variable list. (ver 0.63)

In App tab, you can define the desired application executable. If application executable defined (field value not empty), you can Execute the task (from main screen). (ver 0.65)


if you want to execute application between sync you can define execution parameters here.

  1. Executable name, without parameters (you can use variables here)
  2. Work dir: if you want to define different working dir, specify it here. If this field is empty, the default working dir is the executable directory
  3. Parameters: you can specify app execution parameters here
  4. Generate invoke wrapper (windows only): if you execute application with trigger windows UAC system, some cases the UAC prompt cannot shown, and application execution terminated automatically. If you enable this option, synctocloud generate bat wrapper, and use this, to start execution. After execution ends, generated wrapper bat file deleted.
  5. Wait for exec: wait, until app execution ends (in this case looks like synctocloud app hangs, but it’s doesn’t hang, only waiting)
  6. Wait for process: in some cases, executable start other executable… You can specify process name (or multiple process name, separated with semicolon), and app wait until defined process ends.

The execution flow: Sync app content  – Execute app – Sync app content

If anywhere in this flow Error or Conflict event raised, the flow processing terminated.

TIPP: You can define within task properties the exact execution point (Mode: Always, execute only, preexec, postexec) (ver 0.81)

Leave a Reply