> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/qr/form.md).

# QR form

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). Platforms: web. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/qr/form.md).
{% endhint %}

The public form that a group's QR code opens: a guest reports an issue or makes a request without signing in, then sees a success or a failure page.

![QR form](https://3653879137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsVVGa79QbcEkJ7n8srxe%2Fuploads%2Fgit-blob-3192a0f0bd0fc0bb6db43c9d6d5c4bd7ed3de28e%2Fform.png?alt=media)

The picture shows a group's standard form as it opens: no photo yet, nothing entered and "Submit" disabled.

* **Where:** web only, at qr.snapfix.com `/:id` (the qr\_forms app), where `:id` is the form's ID, the last part of the link in the group's QR code (qr\_forms @ bdfc4f20a5, `src/app/app-routing.module.ts:16`, `src/app/services/form/form.service.ts:28-32`). Guests get there by scanning a printed code or opening its link; signed-in users get a group's codes and link from [Group QR codes](https://docs.snapfix.com/how-the-apps-work/screens/groups/qr-codes.md). Any other address shows the [404 page](#error-pages).
* **Who:** anyone with the code or the link. Nobody signs in, and the page checks no permission. Its calls carry two shared logins that are built into the page's code: the app's Basic login on the form routes, and the Laravel guest login on the AI suggestion routes (`src/app/services/auth-interceptor/auth.interceptor.ts:23-35`). In production the page calls the form routes on `z3.s6eur.com`, not `z3.snapfix.com` (`src/environments/environment.prod.ts:4`) \[[ASK-8](https://github.com/snapfix/docs/blob/main/ASK.md#ask-8-confirm-the-environments)]; the routes are in the [QR API](https://docs.snapfix.com/engineering-reference/api/qr.md).
* **Feature:** [QR forms](https://docs.snapfix.com/product/features/qr/qr-forms.md)

qr.snapfix.com runs the qr\_forms branch `fix/ai-task-creation-photo-capture-image-issue` at its head, 31d98f7, or later: the live page shows "v1.0.9", and its bundle (`main.3677927d80a4d6f0.js`, fetched 2026-11-14) holds code that only that branch has \[[ASK-226](https://github.com/snapfix/docs/blob/main/ASK.md#ask-226-should-master-and-syncyml-follow-the-branch-that-runs-on-qrsnapfixcom)]. This doc describes the live page. Where the branch's code differs, the citations name qr\_forms @ 31d98f7; elsewhere they name qr\_forms @ bdfc4f20a5, whose code is the same there.

## Layout

Top to bottom:

1. **Header:** the title and the header image from the form's layout. An image that does not load is replaced by a default one.
2. **Body:** the fields of the form's type ([Form types](#form-types)).
3. **Footer:** the submit button, which shows a spinner while the form sends, and the footer image.
4. **Version line**, below: "v" and the app version. Builds that are not production show "TEST" first (`src/app/pages/forms/forms.component.html:47`). The line also shows under the result pages, but not on the error pages.

While the form loads, a spinner stands in for the whole page (`forms.component.html:2`, `:44-46`). After a submit, a result page takes the form's place ([After a submit](#after-a-submit)). Google's reCAPTCHA badge shows at the bottom right (`src/styles.scss:136-138`; seen live on 2026-11-14). Apart from the layout's texts and the room names, the page shows no data about the site, the group or its users.

## Form types

The form's type (`form_enum`) decides which page shows. The page reads it from the [form details](https://docs.snapfix.com/engineering-reference/api/qr.md#form-details-object).

| Type             | Page                            | What the guest fills in                         |
| ---------------- | ------------------------------- | ----------------------------------------------- |
| `basic_v2`       | [Standard form](#standard-form) | A photo, where the problem is, notes and a room |
| `dynamic_v1`     | [Custom form](#custom-form)     | The fields its layout lists                     |
| `radiobutton_v1` | [Choice form](#choice-form)     | One choice from a list                          |
| `dropdown_v1`    | [Dropdown form](#dropdown-form) | A photo, a choice from a list and notes         |

* Any other type also shows the custom form (`src/app/pages/forms/forms.component.ts:204-208`, `src/app/shared/enums.ts:1-6`).
* "Generate QR" on [Group QR codes](https://docs.snapfix.com/how-the-apps-work/screens/groups/qr-codes.md) makes a group's standard form. Snapfix staff make custom forms in [QR management](https://docs.snapfix.com/how-the-apps-work/screens/staff/qr-management.md), which has no choice of type (webadmin\_angular @ db972390b8, `src/app/pages/qr-management/components/qr-info-form/qr-info-form.component.ts:28`). The staff API accepts all four types (api\_php\_live\_v2 @ ef3c4319f6, `app/Enums/QrFromType.php:7-10`, `app/Http/Requests/v1/Admin/QrForm/CreateQrFormRequest.php:21`), and the staging database holds live forms of all four types.
* Every text on the page comes from the form's layout (`form_schema`). The standard, choice and dropdown forms fall back to a built-in text where the layout has none. Custom forms have no built-in texts.

## Inputs

### Standard form

"Generate QR" stores the layout with these texts in each standard form it makes (api\_php\_live\_v2 @ ef3c4319f6, `resources/other/dynamicQrForm.php:18-35`); a QA group's form showed them live on 2026-11-14. The layout has no room heading, so the built-in one shows. Built-in texts that differ are given in parentheses. They show only for a layout that lacks the text (qr\_forms @ bdfc4f20a5, `src/app/pages/forms/components/report-issues-form/report-issues-form.component.ts:144-157`, `src/app/pages/forms/components/report-issues-form/basic_v2_default.json:2-23`).

Title: "Report issues, requests and feedback" (built-in "Report Issues").

| Field                                                                                   | Type                                  | Required                                                                                                | Default                                                                                                                                                              | Rules and messages                                                                                                                                                 |
| --------------------------------------------------------------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| "1. What is it?"                                                                        | Photo, from the camera or the gallery | No                                                                                                      | None                                                                                                                                                                 | See [Photo](#photo). Without a photo, the "where" text also goes as the large text that stands in for a photo.                                                     |
| "2. Where is it? \*" (built-in "2. Where is it?")                                       | Text, one line                        | Yes. "Submit" stays disabled while it is empty, with no message; only the "\*" says that it is required | Empty. Placeholder "Exact location is important" (built-in "Exact location is important.")                                                                           | No length limit. Sent as the task's title. The AI suggestion writes its title into this field. A title of only spaces enables "Submit", and the server accepts it. |
| "3. Notes & contact information" (built-in "3. Notes & Contact Information (optional)") | Text, four to eight rows              | No                                                                                                      | Empty. The layout's placeholder is a single space, so none shows (built-in "Explain the issue." and, on a second line, "Your contact information will help us too.") | No length limit. Sent as the task's description.                                                                                                                   |
| "4. Select Room"                                                                        | Select                                | No                                                                                                      | "—" (no room)                                                                                                                                                        | Shown only when the form's site has rooms. Lists the site's rooms by name; a room with no name shows its ID. The choice goes with the task.                        |

Code (qr\_forms @ bdfc4f20a5): `src/app/pages/forms/components/report-issues-form/report-issues-form.component.html:9-55`, `:59`; `src/app/pages/forms/components/report-issues-form/report-issues-form.component.ts:115-141`.

### Custom form

The layout lists the fields as components, and the page shows them in the layout's order. Each component has a kind, a heading (its label, or else its title), a hint and a target, which says where its value goes: the task's title, its description or a chat message. A "\*" after the heading marks a mandatory field. The title, the header and footer images and the button text come from the layout only; with no button text, the button is blank (qr\_forms @ bdfc4f20a5, `src/app/pages/forms/components/dynamic-form/dynamic-form.component.html:1-57`).

| Component                                                         | Shown as                                                                               | Required                  | Rules and messages                                                                                                                                                                                                                                                                                                               |
| ----------------------------------------------------------------- | -------------------------------------------------------------------------------------- | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Photo                                                             | Camera and gallery, with the hint above                                                | If mandatory              | See [Photo](#photo).                                                                                                                                                                                                                                                                                                             |
| Single line                                                       | Text field, with the hint as placeholder                                               | If mandatory              | Title target: at most 50 characters, with a counter "x / 50". Email input: "Email is not valid" under the field for a malformed address, or for one whose last two parts repeat, such as `jane@example.com.com`; the value goes as a chat message that starts with "Email: ". Chat target, or no target: sent as a chat message. |
| Multi-line                                                        | Text area of four to eight rows, with the hint as placeholder                          | If mandatory              | Description target: at most 1000 characters, with a counter "x / 1000". Chat target, or no target: sent as a chat message.                                                                                                                                                                                                       |
| Radio buttons                                                     | One button per option, the hint above the group, and each option's hint as its tooltip | If mandatory              | Options in their sort order. An option marked `default` is selected on load. With the title target, the option's text becomes the title, and its `job_chat_message` goes as a chat message. Otherwise the `job_chat_message` goes as a chat message, or the option's text when it has none.                                      |
| Dropdown                                                          | Select, with the hint as its label                                                     | If mandatory              | As radio buttons.                                                                                                                                                                                                                                                                                                                |
| "Select Room" (added by the page)                                 | Select with "—" and the site's rooms. The layout can rename the heading                | No                        | Only for some sites, see below.                                                                                                                                                                                                                                                                                                  |
| "Enter your email to receive a tracking link" (added by the page) | Text field, placeholder "Enter your email"                                             | No. An empty field passes | Shown only when the layout's success page turns on share links (`enable_shareable_link`). Once the field has been touched, a malformed address shows "Email is not valid" and keeps "Submit" disabled. Sent as `guest_email`, which also goes into the analytics events.                                                         |

* "Submit" stays disabled while a mandatory field is empty or a field is invalid. Only the email fields say why.
* The page leaves out empty fields and a title of only spaces. A form whose title field is optional and left empty sends no title, and the server refuses it with "invalid job title", even with a photo (`src/app/pages/forms/components/dynamic-form/dynamic-form.component.ts:165-240`; authpy @ 5d5758661c, `model/feature_qrform.py:249-250`).
* A layout with two photo, two title or two description components, or an input type other than text or email, gets the [406 page](#error-pages) (`src/app/pages/forms/forms.component.ts:210-235`).
* The room picker depends on two Firebase Remote Config lists of site IDs. Each is a JSON list or a comma-separated text, read again whenever a custom form opens (`dynamic-form.component.ts:371-446`; `src/app/services/remote-config/remote-config.service.ts:9-11`, `:33-41`):
  * `dynamic_qr_room_dropdown_visible`: the sites whose custom forms show "Select Room".
  * `dynamic_qr_customize_task_title_parents`: the sites where a dropdown with the title target also picks the room. The picker stays hidden, and the room is the one whose name matches the chosen option, ignoring case, spaces, punctuation and the word "room", or else the longest room name found in the option's text (`src/app/services/helper/helper.service.ts:175-201`).
* On a site that is not on the first list, and where no title dropdown picks the room, the picker stays hidden, yet a room the AI suggests is still applied and sent with the task, so the guest can neither see nor change it \[[ASK-175](https://github.com/snapfix/docs/blob/main/ASK.md#ask-175-should-custom-qr-forms-show-the-room-picker-for-every-site-with-rooms-and-send-an-ai-room-when-the-picker-is-hidden)]. Where the title dropdown picks the room, that room is sent instead (`dynamic-form.component.ts:411-422`, `:495-499`).

### Choice form

Built-in texts: the title "Help us improve our service", the text "Please choose one of the options below to indicate how enjoyable your dining experience was:", the options "Strongly agree", "Agree", "Neutral", "Disagree" and "Strongly disagree", and the button "Submit". The layout's texts and options replace them (qr\_forms @ bdfc4f20a5, `src/app/pages/forms/components/radiobuttons-form/radiobuttons-form.component.ts:25-37`, `:55-61`, `src/app/pages/forms/components/radiobuttons-form/radiobutton_v1_default.json:2-40`).

* **Choice:** one option, required. "Submit" stays disabled until one is picked, and picking one sends nothing by itself. The options show in their sort order, with none picked at first.
* **Sends:** only the picked option's text, as one chat message. No title, photo or notes go with it, so the server takes them from the form's stored job, and refuses the submit with "invalid job title" when that job has no title (`radiobuttons-form.component.ts:39-53`).
* No room picker and no AI suggestions (`src/app/pages/forms/forms.component.html:14-19`).

### Dropdown form

Built-in texts: the title "Report issues, requests and feedback", "1. What is it?", "2. Select Office Location?" with the label "Exact location is important" and a built-in list of office locations, "3. Notes & Contact Information (optional)" with the placeholder "Explain the issue." and "Your contact information will help us too.", and "Submit" (qr\_forms @ bdfc4f20a5, `src/app/pages/forms/components/dropdown-form/dropdown_v1_default.json:5-12`, `:142-145`).

| Field                                       | Type                                           | Required                                                                                    | Default | Rules and messages                                                                                         |
| ------------------------------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------- | ------- | ---------------------------------------------------------------------------------------------------------- |
| "1. What is it?"                            | Photo                                          | No                                                                                          | None    | See [Photo](#photo). Without a photo, the chosen option's text goes as the large text.                     |
| "2. Select Office Location?"                | Select, labelled "Exact location is important" | Yes. "Submit" stays disabled until one is chosen                                            | None    | Options in their sort order. The option's text becomes the task's title, and its chat message is sent too. |
| "3. Notes & Contact Information (optional)" | Text, four to eight rows                       | Yes, in practice: "Submit" stays disabled while it is empty, though the label says optional | Empty   | Sent as the task's description.                                                                            |

* No room picker and no AI suggestions (`src/app/pages/forms/forms.component.html:20-24`, `src/app/pages/forms/components/dropdown-form/dropdown-form.component.html:10-11`).

Code (qr\_forms @ bdfc4f20a5): `src/app/pages/forms/components/dropdown-form/dropdown-form.component.ts:38-81`, `src/app/pages/forms/components/dropdown-form/dropdown-form.component.html:9-43`.

### Photo

The standard, custom and dropdown forms share this control (qr\_forms @ bdfc4f20a5, `src/app/pages/forms/components/camera/camera.component.ts`, `src/app/pages/forms/components/camera/camera.component.html`).

* **Camera:** the camera starts as the form opens, so the browser asks for camera access then. It asks for the rear camera (`camera.component.ts:28`, `:34-38`; `camera.component.html:2-14`). The capture button takes a picture, cut to the center square and resized to fit 800 by 800 pixels (`camera.component.ts:65-93`).
* **Gallery:** the gallery button opens "Upload image" ([Dialogs and sheets](#dialogs-and-sheets)). It takes JPEG, JPG, PNG and GIF files. Any other file shows "File {name} was rejected. File type not supported." as a short message at the bottom right. The picture is resized to fit 800 by 800 pixels, then the guest crops it (`src/app/pages/forms/components/image-upload-dialog/image-upload-dialog.component.ts:17`, `:29-62`; `src/app/services/helper/helper.service.ts:18-30`).
* **Markup:** on a taken or chosen picture, the tools "Text", "Freehand", "Ellipse", "Frame" and "Arrow" draw on it; "Freehand" is selected first. The marked-up picture is the one that is sent (`camera.component.html:43-69`; `camera.component.ts:162-183`, `:206-243`).
* **Remove:** the close button clears the picture and its markup, and the camera and gallery buttons come back. The form drops the picture. The standard and custom forms also drop the image reference, any suggestion still on its way, a title the AI filled in that the guest has not edited, and a room the AI picked that the guest has not changed (qr\_forms @ 31d98f7, `src/app/pages/forms/components/camera/camera.component.ts:127-140`, `src/app/pages/forms/components/report-issues-form/report-issues-form.component.ts:115-133`, `src/app/pages/forms/components/dynamic-form/dynamic-form.component.ts:149-166`) \[[ASK-226](https://github.com/snapfix/docs/blob/main/ASK.md#ask-226-should-master-and-syncyml-follow-the-branch-that-runs-on-qrsnapfixcom)].
* **Camera unavailable:** when the camera does not start, for example because access was refused, the area shows "Camera permissions have already been denied for this app." and "Open Camera", and the gallery button still works. "Open Camera" checks the camera again and, when it is still unavailable, opens "Permission denied." (`camera.component.html:22-37`; `camera.component.ts:71-75`, `:136-155`). Seen live on 2026-11-14 in a browser that refuses the camera.
* **Button names:** the gallery and capture buttons hold only an image named "Camera", so a screen reader calls both "Camera" (`camera.component.html:29-42`).
* **Sent as:** a file named after the time, with `.png`, whatever its real type (`src/app/services/form/form.service.ts:36`). The server stores it public-read, with no type or size check ([POST /qr-form/{uuid}](https://docs.snapfix.com/engineering-reference/api/qr.md#post-qr-formuuid)).
* **AI suggestions:** on the standard and custom forms, when the site has AI suggestions on (`aiSuggestionEnabled` in the [form details](https://docs.snapfix.com/engineering-reference/api/qr.md#form-details-object)), a picture, taken with the camera or chosen from the gallery, goes to [`POST /v1/guest/suggestions/title`](https://docs.snapfix.com/engineering-reference/api/ai.md#post-v1guestsuggestionstitle) (qr\_forms @ 31d98f7, `src/app/pages/forms/components/camera/camera.component.ts:89`, `:118`) \[[ASK-226](https://github.com/snapfix/docs/blob/main/ASK.md#ask-226-should-master-and-syncyml-follow-the-branch-that-runs-on-qrsnapfixcom)]. A suggested title fills an empty title field, or replaces an earlier suggestion that the guest has not edited; a title the guest typed stays. The field then shows an AI mark until the guest types in it. With the image reference from that answer, the page asks [`POST /v1/guest/suggestions/rooms`](https://docs.snapfix.com/engineering-reference/api/ai.md#post-v1guestsuggestionsrooms) and selects the first suggested room when it is in the list, with the same mark; choosing another room removes the mark (qr\_forms @ bdfc4f20a5, `src/app/pages/forms/components/report-issues-form/report-issues-form.component.ts:72-113`, `:160-170`; `src/app/pages/forms/components/dynamic-form/dynamic-form.component.ts:101-158`).

### Location and reCAPTCHA

These are not fields. The guest sees only the browser's own prompt, and no text about them.

* **Location:** "Submit" first asks the browser for the device location and waits for the answer, with no time limit. When the guest allows it, the latitude and longitude go with the task. When the guest refuses, or on an error, `0` goes in each. The page says nothing about it (qr\_forms @ bdfc4f20a5, `src/app/pages/forms/forms.component.ts:71-92`).
* **reCAPTCHA:** then the page gets a Google reCAPTCHA v3 token for the action "importantAction". When reCAPTCHA gives none, the page sends none, and the server refuses the submit with "invalid authentication", the same words it uses for a wrong shared login. The server's check of the token is in [POST /qr-form/{uuid}](https://docs.snapfix.com/engineering-reference/api/qr.md#post-qr-formuuid) (`forms.component.ts:87`, `:94`, `:133-140`; authpy @ 5d5758661c, `model/feature_qrform.py:145-146`).

## Actions

| Action                                              | Who                               | What happens                                                                                                                                                                                                                                                 | API                                                                                                                                                                                                                                                           |
| --------------------------------------------------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Open the link                                       | Anyone                            | Loads the form, then shows it, or the 404 or 406 page ([Error pages](#error-pages)).                                                                                                                                                                         | [`GET /qr-form/{uuid}`](https://docs.snapfix.com/engineering-reference/api/qr.md#get-qr-formuuid)                                                                                                                                                             |
| Load the rooms                                      | Anyone                            | As it opens, the standard or custom form loads the site's room list. The custom form loads it even when its picker stays hidden. A failed load leaves the list empty.                                                                                        | [`GET /qr-form/{uuid}/rooms`](https://docs.snapfix.com/engineering-reference/api/qr.md#get-qr-formuuidrooms)                                                                                                                                                  |
| Take, choose, mark up or remove a photo             | Anyone                            | See [Photo](#photo).                                                                                                                                                                                                                                         | None                                                                                                                                                                                                                                                          |
| AI suggestions                                      | Anyone, when the site has them on | After a photo, taken or chosen, on the standard or custom form, fills the title and the room ([Photo](#photo)) \[[ASK-226](https://github.com/snapfix/docs/blob/main/ASK.md#ask-226-should-master-and-syncyml-follow-the-branch-that-runs-on-qrsnapfixcom)]. | [`POST /v1/guest/suggestions/title`](https://docs.snapfix.com/engineering-reference/api/ai.md#post-v1guestsuggestionstitle), then [`POST /v1/guest/suggestions/rooms`](https://docs.snapfix.com/engineering-reference/api/ai.md#post-v1guestsuggestionsrooms) |
| "Submit"                                            | Anyone                            | Asks for the location, gets a reCAPTCHA token and sends the form, then shows the result ([Submit](#submit)).                                                                                                                                                 | [`POST /qr-form/{uuid}`](https://docs.snapfix.com/engineering-reference/api/qr.md#post-qr-formuuid)                                                                                                                                                           |
| Repeat button ("Report another issue", "Try again") | Anyone                            | Shows the same form again, empty, with a new session ID for analytics. After a failure, everything entered is lost.                                                                                                                                          | None                                                                                                                                                                                                                                                          |
| Share link                                          | Anyone                            | Opens the task's read-only page in a new tab.                                                                                                                                                                                                                | None                                                                                                                                                                                                                                                          |
| Promotion button ("Learn more", "Learn More")       | Anyone                            | Opens the layout's link in a new tab; the built-in link is <https://snapfix.com/>.                                                                                                                                                                           | None                                                                                                                                                                                                                                                          |
| "Open Camera"                                       | Anyone                            | Checks the camera again, and opens "Permission denied." when it is still unavailable.                                                                                                                                                                        | None                                                                                                                                                                                                                                                          |
| <support@snapfix.com>                               | Anyone                            | On the error pages, opens an email to support.                                                                                                                                                                                                               | None                                                                                                                                                                                                                                                          |

Code (qr\_forms @ bdfc4f20a5): `src/app/pages/forms/forms.component.ts:60-65`, `:84-131`, `:142-179`; `src/app/pages/forms/components/report-issues-form/report-issues-form.component.ts:180-200`; `src/app/pages/forms/components/dynamic-form/dynamic-form.component.ts:448-472`; `src/app/pages/forms/components/form-status/form-status.component.html:14-19`, `:24-28`, `:39-43`; `src/app/pages/page-not-found/page-not-found.component.html:12`.

## Submit

```mermaid
flowchart TD
  A[Open the link] --> B{Form details}
  B -->|result false or error| C[404 page]
  B -->|custom layout fails the checks| D[406 page]
  B -->|ok| E[Form]
  E --> F[Submit]
  F --> G{Result}
  G -->|result true| H[Success page]
  G -->|result false| I[Alert and failure page]
  G -->|no answer| J[Failure page]
  H -->|repeat button| E
  I -->|repeat button| E
  J -->|repeat button| E
```

1. "Submit" is enabled once the required fields have a value. The custom form disables it as soon as the send starts. With a picture, the standard and dropdown forms first wait for the marked-up picture, at least half a second, and keep "Submit" enabled meanwhile. If the picture is not ready within about five seconds, the wait never ends and nothing is sent. A second press during the wait runs the steps again, which can send the form twice or leave both presses waiting (qr\_forms @ bdfc4f20a5, `src/app/pages/forms/components/report-issues-form/report-issues-form.component.ts:115-120`, `src/app/pages/forms/components/camera/camera.component.ts:162-183`, `src/app/pages/forms/components/dynamic-form/dynamic-form.component.ts:165-172`).
2. The page asks for the location, then gets the reCAPTCHA token ([Location and reCAPTCHA](#location-and-recaptcha)).
3. The page posts the fields as form data to [POST /qr-form/{uuid}](https://docs.snapfix.com/engineering-reference/api/qr.md#post-qr-formuuid), as the table below lists (`src/app/services/form/form.service.ts:34-40`, `src/app/services/helper/helper.service.ts:86-114`).
4. The page shows the result ([After a submit](#after-a-submit)). The submit also logs analytics events that carry the sent values (all but the photo and the token), the location and the session ID (`src/app/pages/forms/forms.component.ts:96-122`, `:237-246`).

What each form sends:

| Form     | Fields                                                                                                                                                                                                                               |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Standard | `fTitle`, `fDescription`, the photo as `uploaded_image` or else the title again as `fLargeTextTitle`, the room as `roomUUIDs[]`, `aiTitle`, `aiTitleSuggestion` and `imageRef`                                                       |
| Custom   | The title, the description, the photo and the chat messages (`jobchats`) that its components fill, `fLargeTextTitle` when there is a title and no photo, `guest_email`, `roomUUIDs[]`, `aiTitle`, `aiTitleSuggestion` and `imageRef` |
| Choice   | `jobchats`, with the picked option                                                                                                                                                                                                   |
| Dropdown | `fTitle`, `fDescription`, `jobchats`, and `uploaded_image` or else `fLargeTextTitle`                                                                                                                                                 |

* Every form adds `fLat` and `fLng`, and `recaptcha_token` when there is one (`src/app/pages/forms/forms.component.ts:84-94`). `imageRef` goes only when the title suggestion gave one, and `roomUUIDs[]` only with a room.
* The standard and custom forms also send `aiRoomSuggestion`: 1 when the room sent is the one the AI suggested, and 0 otherwise (qr\_forms @ 31d98f7, `src/app/pages/forms/components/report-issues-form/report-issues-form.component.ts:145`, `:152`, `src/app/pages/forms/components/dynamic-form/dynamic-form.component.ts:257`) \[[ASK-226](https://github.com/snapfix/docs/blob/main/ASK.md#ask-226-should-master-and-syncyml-follow-the-branch-that-runs-on-qrsnapfixcom)].
* The page never sends the group, the creator or the stored job's other keys. A hand-made request can set the group and the creator, and some of the other keys make it fail.

## After a submit

The result page has the header, a text, the job reference, the share link when there is one and a repeat button, and below them a promotion block (qr\_forms @ bdfc4f20a5, `src/app/pages/forms/components/form-status/form-status.component.html:1-44`). Each text comes from the layout's `page_success` or `page_fail`; the standard, choice and dropdown forms fall back to the built-in text where the layout has none (`src/app/pages/forms/components/form-status/form-status.component.ts:20-36`). Custom forms show only the layout's texts. No form was submitted in the live pass, so these pages are known from the code only.

| Result                              | What shows                                                                                                                                                                                                  | Standard form                                                                                            | Built-in                                                                    |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Accepted (`result` true)            | The success page: the title, the text, "Ref: \[]" with the task's reference, the share link with "Click the link to track progress of this task." when the form turns on share links, and the repeat button | "Thank you!", "Issue submitted successfully", "Report another issue"                                     | "Thank You!", "Issue submitted successfully.", "Report Another Issue"       |
| Refused (`result` false)            | An alert with the server's message and "Ok", over the failure page: the title, the text and the repeat button                                                                                               | "Something went wrong!", "Your submission did not go through." (the layout's text is empty), "Try again" | "Something went wrong!", "Your submission did not go through.", "Try again" |
| No answer (network or server error) | The failure page only, with no alert                                                                                                                                                                        | As above                                                                                                 | As above                                                                    |

* **Alert:** on the standard, choice and dropdown forms its title is always "Something went wrong!"; on a custom form it is the layout's failure title, or "Something went wrong!" when there is none. The message is the server's text as it comes, such as the per-form limit text, "invalid authentication", "invalid recaptcha", "invalid job title" or "invalid job image". Every message is under Errors in [POST /qr-form/{uuid}](https://docs.snapfix.com/engineering-reference/api/qr.md#post-qr-formuuid) (`src/app/pages/forms/forms.component.ts:106-111`, `:193-202`).
* **Promotion block:** a logo, a main image, a text and a button that opens a link in a new tab. On the standard form the text is "The simplest maintenance platform in the world.", with "Learn more" on the success page and "Learn More" on the failure page (api\_php\_live\_v2 @ ef3c4319f6, `resources/other/dynamicQrForm.php:4-17`, `:36-49`). The built-in block has the same text with a line break after "maintenance", the button "Learn More" and the link <https://snapfix.com/> (qr\_forms @ bdfc4f20a5, `src/app/pages/forms/components/report-issues-form/basic_v2_default.json:30-36`).

### What a submit creates

All of this happens on the server; [POST /qr-form/{uuid}](https://docs.snapfix.com/engineering-reference/api/qr.md#post-qr-formuuid) has the details.

* **A red task** in the group that the form's stored job names; the page sends no group. Its content is the photo, or the title as large text. The task gets a "Created Task" chat item, the stored job's own chat items and the chat messages that were sent.
* **A push** to the group's admins, the members who may view all tasks, and the task's assignees and followers, through an apipy route that takes no login.
* **A share link** that lasts one year, when the layout turns on share links, and an email "Your Snapfix Task Link" with that link, when the guest also typed an address \[[ASK-174](https://github.com/snapfix/docs/blob/main/ASK.md#ask-174-should-new-custom-qr-forms-send-a-tracking-link-by-default)].
* **No text message.**
* **The photo**, stored public-read in an image bucket named as a test bucket, in every mode \[[ASK-173](https://github.com/snapfix/docs/blob/main/ASK.md#ask-173-should-qr-photos-keep-going-to-the-bucket-named-testimagessnapfixio)].
* **Analytics events** in Firebase Analytics, with the typed text, the guest's email and the location. Camera events go out under the codes of other events (qr\_forms @ bdfc4f20a5, `src/app/services/fire-event/fire-event.service.ts:22-32`, `src/app/services/fire-event/fire-events.json:14-21`).
* **Other services:** the page loads Google's reCAPTCHA script with the form, and custom forms read Firebase Remote Config (`src/app/app.module.ts:46-52`). With AI suggestions on, the photo, and then the site's ID and the image reference, go to the guest suggestion routes ([AI API](https://docs.snapfix.com/engineering-reference/api/ai.md#post-v1guestsuggestionstitle)).
* **Logs:** authpy keeps the whole request, the guest's email and the reCAPTCHA token included.

## States

* **Loading:** a spinner stands in for the page while the form loads. While a send runs, "Submit" shows a spinner and stays disabled.
* **Empty:** with no rooms, the room picker does not show. With no photo, the camera shows, or the "Open Camera" block when the camera does not start.
* **Error:** the 404 page for a wrong, deleted or expired code, for any other refusal of the form call, and for a failed call. The 406 page for a custom layout that fails the checks. An expired form shows the 404 text, not the 406 one; no code sets an expiry yet. For a refused or failed submit, see [After a submit](#after-a-submit) (qr\_forms @ bdfc4f20a5, `src/app/pages/forms/forms.component.ts:142-179`).
* **No permission:** not applicable, since no account is needed. Camera and location are browser permissions ([Photo](#photo), [Location and reCAPTCHA](#location-and-recaptcha)).
* **Offline (mobile):** not applicable, since the page is web only. Without a network, a submit ends on the failure page with no alert.

## Error pages

* **404:** the Snapfix logo, "This QR appears to be incorrect", "Please contact your administrator or email us at <support@snapfix.com>" (the address is an email link) and the code 404 below. Any address other than `/:id` shows it too (qr\_forms @ bdfc4f20a5, `src/app/app-routing.module.ts:15-18`, `src/app/pages/page-not-found/page-not-found.component.html:1-14`).
* **406:** the same page with "This QR form is not currently active" and the code 406 (`page-not-found.component.html:8`).

## Dialogs and sheets

* **"Upload image":** "Drag and drop an image here", "OR" and "Choose an image"; the guest drops a file there or picks one. The crop step follows for the chosen picture, with a close mark that goes back to the drop area. "Cancel" closes the dialog; "Save" stays disabled until a file is chosen, then adds the cropped picture (qr\_forms @ bdfc4f20a5, `src/app/pages/forms/components/image-upload-dialog/image-upload-dialog.component.html:1-35`, `src/app/pages/forms/components/image-upload-dialog/image-upload-dialog.component.ts:54-68`).
* **"Permission denied.":** "Camera permissions have previously been denied for this browser. Please go into your settings and enable camera permissions." and "Note: you can also use the gallery button to add an image from your gallery.", in the alert's layout with "Ok" (`src/app/pages/forms/components/camera/camera.component.ts:136-155`).
* **Alert:** a title, a message, a close mark and "Ok" ([After a submit](#after-a-submit); `src/app/pages/forms/components/alert-dialog/alert-dialog.component.html:1-12`).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/how-the-apps-work/screens/qr/form.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
