When you create a form with Form Builder, you pick an application name and form name for that form. For instance, for a marriage registration, you might choose
clerk as the application name, and
marriage-registration as the form name.
When you publish the form, assuming you have Orbeon Forms deployed on a server on
http://www.city.gov/forms, citizen will be able to fill out a new marriage registration by going to
In a typical deployment, users will access this page from another part of your web site or web application that contains a link to form served by Orbeon Forms. For instance, a city government might have on its web site a page listing forms citizen can fill out, which links to the marriage registration form on
Linking doesn't make any assumption on the technology used by the web site or application you're linking from. Your site could use Drupal, WordPress, be served by IIS, using .NET, or any other technology. For instance, the diagram below is for a situation where your web site is served by Microsoft IIS, implemented in .NET, and links to forms served by Orbeon Forms.
/fr/clerk/marriage-registration/new in our example is what is referred to below as a path, and for a given form, multiple such paths exist. Knowing what those paths are is particulary important as this allows you to link from your web site or web application to forms your created with Form Builder. All the paths are relative to the deployment context, i.e. where you've deloyed Orbeon Forms, which in our example was
Summary page for a given form definition:
New empty form data:
Edit existing form data:
Read-only HTML view:
Read-only PDF view:
Read-only TIFF view: [SINCE Orbeon Forms 2016.1]
When using versioning, you can pass the
form-version URL parameter:
By default, the latest available form definition version is used.
[SINCE Orbeon Forms 2018.1]