Form AI Agent

The Form AI Agent brings the same LLM-powered assistant to the form editor. From the Form Agent panel you describe the form you need in natural language, and the agent builds it or changes the one you have open — fields, validation, visibility rules, layout, groups, tables, and computed values. Answers about an existing form are available too, without changing anything.

It is the same agent as the BPMN AI Agent, reached from the form editor instead of the canvas, and it uses the same providers and models — there is nothing extra to configure.

Using the Agent

Open a form, then open the Form Agent panel from the modeler toolbar. It docks beside the editor and behaves like the diagram panel: float, resize or collapse it, dictate a request by voice, attach files, and Stop a running request at any time. Each conversation is kept as a session, separate from the diagram agent’s sessions.

Two modes:

• Edit — build or change the form. The agent returns the complete schema, which you apply.
• Ask — answer questions about the form without touching it: which process variables it writes, whether required fields are reachable, whether two fields collide on the same variable.

Example requests:

• “Build a customer onboarding form: company name, VAT number, contact email (required), phone, and a checkbox to accept the terms.” (edit — from an empty form)
• “Make the phone field required and only show it when the terms checkbox is ticked.” (edit)
• “Put company name and VAT number side by side.” (edit — layout)
• “Add a table listing the invoice positions from the process variable positions, with description and amount.” (edit)
• “Which process variables does this form write?” (ask)

Attachments work as they do on the diagram side, and are useful here: attach a screenshot or a PDF of a paper form and ask the agent to reproduce it, or attach an existing .form schema to start from it.

Reviewing and Applying Changes

Nothing reaches the form until you say so. When the agent returns a schema, the panel shows a card with what applying it would do, read from the schema itself rather than from the agent’s description of its own work:

The form is ready to apply.
  Removes: Upload Invoice PDF
  Adds: Phone Number
  Changes: Amount
[Apply] [Discard]

Apply imports the schema into the editor; Discard leaves the form untouched. Enable Auto-accept in the compose box to skip the card and apply every change immediately.

Read the summary before applying, particularly the removals: importing a schema replaces the form, and the editor cannot undo it. A form you have saved before can be recovered from its snapshots; an unsaved change cannot.

An applied schema behaves like your own edit: Save stores it and records a snapshot, and where autosave is enabled it is saved for you like any other change.

What the Agent Can Build

The agent works on the form’s form-js schema and knows the components the editor offers:

• Inputs — text, textarea, number, checkbox, checklist, radio, select, tag list, date and time.
• Validation — required, minimum and maximum, length, a regular expression with its own message, and the email and phone types.
• Visibility and read-only state — FEEL expressions such as =not(accept_terms).
• Layout — fields side by side on a row, with their widths.
• Groups and dynamic lists — including the path that nests their values into one object, when you ask for it.
• Tables — bound to a process variable, with the columns to show.
• Computed values — an expression field that derives a value instead of asking for one.
• File upload — a file picker; CIB seven uploads the chosen file and the process receives it as a File variable.

Limitations

Everything in the diagram agent’s limitations applies here — review what it produces, expect different results on different runs, and watch the context budget. In addition:

• Ask before you trust a claim. A smaller model sometimes describes more than it did, for instance reporting that a column now shows a currency when the schema cannot express that. The card’s summary is computed from the schema, so read it rather than the reply.
• Table columns carry a label and a field only. There is no per-column formatting: a value that needs a unit or a currency has to arrive formatted in the process data.
• A document preview needs document metadata. It renders only when the process supplies its data source with a document id and a reachable endpoint; nothing in CIB seven produces that on its own.
• Properties the editor does not know are dropped silently. If a request cannot be expressed in a form schema, the agent should say so — but a field that looks configured and does nothing is the failure mode to watch for.
• No plan mode. Forms are changed in one step; the plan and step-by-step execution of the diagram agent do not apply.
• DMN is not supported yet. The agent works on diagrams and forms.