Start processes after a form submission

A customer form or public web form can be linked to an active KimProcesses template. After successfully creating the ticket, Qisutu starts that template automatically. Forms remain a core feature; process execution requires the add-on.

Prerequisites and selection

KimProcesses must be installed, active and enabled in its own settings. An active process template must also exist. Only then is the template selection usable in the form. If the section is entirely missing, first check module status and settings, not the form language.

  1. Under Administration → Forms, open the customer or public form.

  2. Check the destination queue, form texts, fields and customer access or public embedding settings as usual.

  3. Select the active template under Start process automatically.

  4. Save the form.

  5. Submit the form with a test contact and all required fields completed.

  6. Open the resulting ticket and check the started process instance or its outcome in KimProcesses.

Do not start a process leaves normal ticket creation unchanged. Configuring an existing form does not start processes retrospectively for its previously created tickets.

What happens if the process fails

Successful ticket creation and successful process startup are different outcomes. If startup or the first process step fails, the ticket and normal form confirmation remain intact. Qisutu adds an internal note containing the process name and error. The customer should not resubmit the form merely because of this failure.

Check the internal article Automatic process start failed, then the template and module configuration. Disabled or unavailable KimProcesses does not start a process. Process steps are defined in the add-on, not by the Qisutu form.

Form attachments and standard tickets

Customer and public forms support multiple attachments. Configured size limits also apply here; a file exceeding the limit must be removed or reduced before resubmission.

In system settings, Standard ticket in addition to forms can keep ordinary customer ticket creation available alongside custom forms. This does not enable a process template for standard tickets: automatic startup is linked to the configured form.