Appearance

Engine Editor ​

The Engine Editor is the admin web app's workspace for questionnaire engines. It lists the engines available to the instance, lets you inspect and edit an engine's components in the browser with a live preview, and publishes the result to the instance's engine store. It is found under Admin panel → Engines.

Engines list ​

The list shows every engine registered on the root folder configuration, with its version, the core it is built on and its status. From here you can open an engine in the editor or create a new one. A second panel lists published versions present in the engine store, with links to each version's manifest and bundle, and lets you remove versions that are no longer used.

Which engines a folder offers, and therefore which engines the create-questionnaire dialog proposes, is part of folder configuration and is inherited by nested folders. See Folders & Configuration.

Creating an engine ​

Create engine asks for a name, an identifier, a version, an icon and the core to build on (chosen from the cores registered on the folder). The new engine starts with no components; add them one by one or start from an exported manifest of an existing engine.

Editing components ​

The editor is a full in-browser development environment:

  • A picker switches between the engine's components and its shared files.
  • Each component has its own file set: the component source, its settings schema and the settings form layout.
  • The preview on the right renders the selected component inside the core, at phone size, with a sample question of that type (Mobile tab), and renders the settings form generated from the schema (Form tab). Changing the settings in the form immediately changes the sample question.
  • Undo/redo covers component edits; Export downloads the complete engine manifest so it can be versioned in your own repository or loaded with the builder tool.
  • A developer output toggle reveals the compiled output for authors who need it.

Component metadata (name, label, icon, main file) is edited through a small dialog; deleting a component removes its question type from the engine.

AI assistance ​

The AI assistant is available inside the editor and understands the engine you have open. It can inspect the engine and its components, create or update component files and shared files, change component metadata, and switch the editor to a component, all while you watch the preview. Ask it for a new question type, a translation, or a validation rule, then review the diff before publishing. See AI Assistant.

Publishing ​

Publish builds the engine from its manifest on the server and uploads the bundle and manifest to the instance's engine store, where it appears in Published versions. Publishing requires the engine builder feature to be enabled for the instance and the corresponding permission on your role. Increase the version before publishing a change; versions are immutable once questionnaires are bound to them.

Binding a questionnaire to an engine ​

  • New questionnaires are bound to an engine when they are created; the dialog offers the folder's engines.
  • Existing questionnaires show their engine on the configuration page's Engine tab: name, version, core, the supported question types with their icons, the runtime configuration form (the engine's options, for example paged or scrollable display) and the technical manifest. Change Engine rebinds the questionnaire to another engine by URL; the designer palette then shows the new engine's question types.

Changing the engine of a questionnaire that uses question types the new engine does not provide is refused until those questions are removed or converted.

Engine options ​

Options exposed by the core's configuration schema appear as a form on the questionnaire's Engine tab and are stored with the questionnaire, so every host applies them. The default core exposes the display mode (paged or scrollable). Custom engines can expose further options by extending the schema in their manifest.

File upload settings ​

Question settings forms are rendered with the platform's form engine and support a file upload control, which lets a question type accept a file reference (an image for an instruction page, for example) as part of its settings.