# CQL search field {appHash}_capable_forms_form_ids

A genuine Confluence search alias declared by both apps, shown in the Capable CQL editor as "Forms on page (ids)" with operators = and IN. The literal field name embeds the app hash, so it DIFFERS between the standalone Forms app and the Suite - a saved CQL search does not carry over when a customer moves from one to the other.

---

## Where you do it

| **Task**                                | **Where**                                                   |
| --------------------------------------- | ----------------------------------------------------------- |
| Insert the form container               | Confluence page editor, macro browser                       |
| Give the form a Form ID and a Form name | Form macro config panel ("Configure Form")                  |
| Place fields inside the form body       | Confluence page editor, inside the Form macro's body region |

---

## Settings that affect this

| **Setting**                             | **Where**                                  | **What it does**                                                                                                                                                                     |
| --------------------------------------- | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Space Capability Settings → Forms (Auto | Space settings → Space Capability Settings | Per-space visibility of the Forms byline entry. Space Admin only - others see "You must be a Space Admin to change these settings.".                                                 |
| Advanced edition                        | Marketplace / licensing                    | Unlocks every input type beyond single-line text, and unlocks the Forms nav item in the Suite regardless of the flag. It does NOT unlock the Forms search panel - that is flag-only. |

---

## Limits that apply here

| **Limit**                             | **Value**                                | **What happens**                                                                                                              |
| ------------------------------------- | ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Responses table page size             | 25 rows                                  | The per-form responses table pages 25 pages at a time using search cursors. Next/Previous and Refresh only - no jump-to-page. |
| Pinned forms in the catalogue sidebar | 10 per user                              | Opening an eleventh form drops the oldest.                                                                                    |
| Standalone field autosave delay       | 800 ms after the last change; "Saved" ti | Applies only to Input macros outside a Form container.                                                                        |

---

## Worth knowing

* The edition gate is inconsistent by placement: the config panel blocks you from CREATING an Advanced field on Standard, and a STANDALONE Advanced field hides both its control and its saved answer - but an Advanced-typed field already inside a Form container renders and stays fillable on Standard, because the form renderer never consults the gate.
* Two fields on the same page that share a Field ID collapse into one entry in the indexed answers; the later silently overwrites the earlier.
* Changing a field's Input type wipes the stored answer and drops settings that do not apply to the new type.
* A URL field's placeholder cannot be set from the config panel, even though the stored value would be honoured - the panel simply does not offer the box for that type.
* There is no layout control at all: no columns, sections, page breaks or conditional fields. A form is exactly the vertical run of fields in its body.
* Field numbering means different things in the two placements: a standalone field is numbered by its position among all Input macros on the page; a field inside a form is numbered within that form's body.

---

## Related

[Confluence labelsAnother connection.](https://help.gocapable.com/forms/confluence-labels.html)

[Site-wide Form ID registryAnother connection.](https://help.gocapable.com/forms/site-wide-form-id-registry.html)

[IntegrationsEvery connection.](https://help.gocapable.com/forms/integrations.html)

---

_Better with company._