The notion of publishing is central to Form Builder/Form Runner.
As a form author, you first work on a form definition in a special space where the form can be modified, saved, and tested.
Once the form definition is ready, you publish it to Form Runner.
After that moment:
the form becomes available by form users for data entry
Form Builder is no longer part of the equation
When you start publishing a form with the Publish button at the bottom of Form Builder, a dialog opens to confirm the application name form name:
If you decide to go ahead with publishing, simply use the Publish button.
[SINCE Orbeon Forms 2017.2]
You can decide whether the published form is available to end users with the "Make published form available" option. You can later change the availability of the published form either in Form Builder by re-publishing it, or from the Form Runner runner Home page. By default the form is made available.
When versioning is enabled, you have a choice, when publishing, of whether to create a new form version or to overwrite an existing one.
When creating a new form version, publishing the form definition creates a new version of the form definition in the database. Data which already exists in the database will still be viewed and edited with the previous versions of this form definition which are associated with that data. The new form definition version will be used to create, edit and view new data.
When overwriting an existing form definition, if the changes you have made to the form definition are small and non-structural, such as changing control labels only, the form definition will be compatible with existing form data. But if you have made structural changes, such as adding, removing, renaming, or moving controls, the form definition might be incompatible with existing data. We recommend being careful when overwriting an existing form definition version.
See also versioning for details about the implications of these options.
[SINCE Orbeon Forms 2016.1]
You can overwrite not only the latest published version, but any previous version.
[SINCE Orbeon Forms 2016.2]
You can add or update a textual comment associated with the given published version. Adding a comment is not required, but setting a comment can help the form author understand what changes a given form version includes.
When creating a new version, the field is initially empty:
You can set an explanatory comment:
When overwriting an existing form version, the existing comment, if any, is read back from the published form definition and you can update it before publishing: