Public forms

Public forms run through form.pl outside the normal sign-in process.

Overview

This page explains how to use Public forms and describes its main effects. Test changes in a test environment first whenever they may affect existing tickets, permissions, notifications, or automations.

Typical workflow

  1. Load a form using its URL identifier. Use the available search, filter, and detail views. Clear or change filters if expected records do not appear.

  2. Use public CSRF protection. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

  3. View field definitions and dynamic values. Use the available search, filter, and detail views. Clear or change filters if expected records do not appear.

  4. Validate the submission and create a ticket. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

  5. Assign the contact to the internal customer QISUTU-WEBFORM. Open the existing record, change only the required fields, and check dependent assignments before saving.

  6. Retain the submission snapshot on the ticket. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

  7. Apply rate limits by form, IP address, and day. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

Notes

  • Visible menu items and actions depend on the signed-in agent’s group and program permissions.

  • Deactivated entries are often retained for existing tickets and reports, but are no longer available for new assignments.

  • After making changes, test at least one realistic use case with a user in the affected role.