This page is accessible using “Tasks” entry on the window top menu.

A task is composed of 2 entities :

• On the puppeteer, the tasks' definition including parameters. You have to keep in mind that parameters are fully dynamics, meaning a puppet will receive parameters effective at the time of execution. In other word, if you create a task with A as parameter, you submit it, you change its parameter to B and then the puppet is able to run it, B will be took in account, not A. Idem if you delete a task before the puppet takes it, the task will be rejected as invalid.
• On the other side, the puppet has to known this task. Technically, it means a script corresponding to the tasks name exists in puppet's TasksScripts directory. If it doesn't exist, the puppet will reject the task as unknown. This way of working provides security as only deployed tasks can run on a particular puppet, whatever is the policy of others puppets.

• A task is identified by its name, that has to be unique to the puppeteer. This name has to match puppet's script.
• Optionally, an argument. More information can be found in tasks' repository.
• a comment. This field is totally free and is not used at all by the system.

Usually, a new task is launched only when the previous task is finished. But tasks marked as fast don't have to wait : they are executed whatever is the activity ongoing on a puppet.
This kind of task is generally reserved for punctual, non resource consuming and light tasks. The good example should be a task requesting about disk usage or about CPU load.

Some tasks are part of a puppet's queue but have to run at Puppeteer side. As example, mail notification, selection of the next entity of a group ...
For such tasks, Puppeteer's tasks has to be checked and a drop down list will appear to select which kind of task to run.