Forms and submissions
A form is an input to a workflow. Describe its fields, validation, where submissions are saved, and who can read or act on them.
Define the result
Section titled “Define the result”Create a request form with name, email, category, and message. Save accepted submissions with a status of New. Show a confirmation with a reference, and let staff review the queue.
Test submission behavior
Section titled “Test submission behavior”Submit a valid example and verify the saved record. Try missing and invalid fields, a slow response, and a repeated click. Confirm that a failed save does not show a success message or send a misleading acknowledgment.
If files are accepted, define formats, size limits, and access. Use the limits available to your app; a form design does not establish unlimited uploads or submissions.
Add a useful next step
Section titled “Add a useful next step”Email can acknowledge a saved request. A language model can propose a category or summary for review. Keep the original submission alongside derived information so staff can check it.