There are two ways forms can invoke this trigger. You can either select that every form sets off this trigger, regardless of the submission type, or that only a specific form sets off this trigger.

• Trigger for every form: Every form executes the task. Although the data entered in the form is passed as a parameter, it is not displayed because all forms contain different fields. The trigger mode for all forms is particularly suitable for notifications, especially if there are only a few tasks in the system.

• Trigger for a specific form: In this case, the form must have the transmission type Forms that notify the Task Planner set. The trigger now has access to all fields that have been set in the form. However, it should be noted that in this mode, no ticket is created or changed. The form serves solely for the purpose of executing a task.

• Users can be notified via pop-up or email when a specific or any form has been executed. This can be used for formular performance monitoring, for example.
• When using specific forms, tickets can be created in one go, e.g., via QuickTicket, and assigned to a process. This provides a high degree of flexibility that goes beyond the direct creation of a ticket.

Note: If the form is used in QuickTickets or text modules using the placeholder [form.url], it is automatically replaced by the complete URL including the protocol. In this case, the rich text editors ask whether the URL should be created with a preceding "https://". It is essential to select "no" here, as otherwise the URL will contain the protocol twice.