A launch form is the set of questions shown when someone starts a task. Every task asks for a description ("Describe the task"), which becomes the task's name. Extra fields let you collect more, such as a candidate's name, a start date or a budget.
Each extra field becomes a task variable, available to every item in the task as {{field_name}}.
Go to Settings → Extra fields in the workflow editor and add fields. Each field is defined with directives, in the same format as template fields:
--#: ---name:candidate_name ---type:text ---appears_on:settings ---mini_label:Candidate's full name ---required:true --#: ---name:start_date ---type:date ---appears_on:settings ---mini_label:Start date --#: ---name:contract_type ---type:dropdown ---appears_on:settings ---mini_label:Contract type ---options:"Permanent","Fixed term","Freelance"
Launch form fields always use ---appears_on:settings. For every directive and field type, see Template field directives.
When a task is started through the API, its variables come from the passed parameter and any other POST fields instead of the launch form. Use the same names as your launch form fields, so the workflow works either way. See API: Starting tasks.
In Advanced workflow settings, ---example_description: adds a hint next to the task description field, such as "(e.g. Jane Smith, Sales Manager)".
Task variables set at launch can't be overwritten by an item's ID or alias of the same name. Don't give an item the same ID or alias as a launch form field.