Working with other capabilities

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

Most of what makes Forms worth having in the suite comes from what sits next to it. This page is the summary; each connection has its own page with the detail.

Where a connection does not exist, it is listed as such rather than left out, so you can stop looking.

#Every connection

Connects to

What you get

Where a response lives

In the page's own content. Save writes each field's answer back into that Input macro's stored parameters in the page document, as the signed-in user. Responses therefore inherit Confluence page permissions exactly and travel with a page copy.

Page content property {appHash}_capable_forms

A mirrored, read-only index on the page holding, per Form ID: the form name, a map of field snapshots keyed by field ID (label, input type, text value, list value), plus updatedAt and updatedBy. Rebuilt immediately after a successful Form Save and again from page and blog-post create/update events.

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

Confluence labels

Forms adds Confluence global labels to customers' pages as the app: capable_forms_page on every page carrying a form, plus one capable_forms_{formId} per form. Labels matching that prefix that Forms no longer wants are deleted. Only labels matching those patterns are ever touched.

Site-wide Form ID registry

A tenant-wide index of distinct Form IDs holding form name, page count and last seen. Diffed per page: adding a form increments the count, removing it decrements, and the entry is deleted at zero. This is what feeds the catalogue's All forms table.

Confluence global page "Capable Forms"

The global page that hosts the Forms catalogue. Reachable by unlicensed and anonymous visitors, who get the static Capable visitor notice instead of the catalogue.

Confluence space page "Capable Forms"

The same catalogue opened inside a space, where the responses table is scoped to that space. Also reachable by unlicensed and anonymous visitors, who get the visitor notice.

Capable Sites static export

A published Capable Site renders both macros as READ-ONLY, disabled HTML controls: text, long text, number, radio, checkbox and select all render disabled with their saved values; a URL field renders as a plain link (an unsafe stored URL is never made into a live anchor); and user, space and page fi

Usage metric

Every successful Form Save records a business usage metric for the Forms capability.

Server surface

Exactly two operations exist: save the fields on a page, and list the Form ID registry. Both require a signed-in account; an anonymous caller is rejected.

#The pages

#A few things worth knowing

  • A connection needs both halves installed. In a standalone app most of these do not exist.

  • Anything that depends on search only reflects pages that have been indexed.

  • Published sites render Capable macros properly, which is where several of these pay off.

Better with company.