The Orbeon Forms Blog

Orbeon Forms allows you to manage your web forms' entire lifecycle, and run your forms on-premises or in the cloud, with a focus on security and compliance.

What happens after users fill out a form?

Orbeon Forms focuses on making it easy for form authors to create and deploy forms, and for end users to fill out those forms. When you create and deploy a form with Form Builder, you get the URL of a new page for that form. You can point users to... More

Orbeon Forms 4.0 M1

Today we released Orbeon Forms 4.0 M1 (Milestone 1). As the name implies, this is not a final release, but a release aimed at people who want to have a preview of what’s going to be in the upcoming 4.0 release and, hopefully, send us some feedback. Most features planned... More

Run modes

Recently, we implemented support for run modes in Orbeon Forms. The idea is not new and it comes down to this: sometimes you want to run Orbeon Forms with development settings, and sometimes with production settings. So far, to achieve this, you had to play with your properties-local.xml file, either... More

Forms access control with Form Builder

Who can do what with Form Builder? You guessed it: in this post, we’ll discuss access control, as it relates to Form Builder. More specifically, that question has two facets: When it comes to people using Form Builder to create or edit forms, often referred to as form authors, who... More

More XForms bindings

Photo by preservationgal In a previous post, we covered the basics of controls bindings, where XPath expressions are used to bind a control to XML elements. But it’s not always that simple, is it? So now is the time to cover all the cases you can encounter with binding expressions. First, there... More

How XForms controls bind to data

Photo by Philippa Willitts Take the most basic HTML input field: <input name="nickname"> Then, compare to the equivalent XForms: <xforms:input ref="nickname"> Both look pretty much the same, right? Well yes, but only on the surface! In HTML, you just specify a name, which is later used by form submission (or to... More

Form Runner gets a home page

For every form you create with Form Builder, after you deploy the form, Orbeon Forms exposes two pages: A new page, which end users go to to fill out the form. When a form is filled out and saved, it creates what we refer to as form data. A summary... More

XForms 2.0: goodbye nodeset

XForms 1.1 makes a distinction between two commonly-used attributes: ref and nodeset. Both are binding attributes, and they hold an XPath expression pointing to zero, one or more XML element or attribute nodes: ref points to a single node ("single-node binding"). Its most frequent use is to bind a control such as xforms:input to XML data. nodeset points to... More

Support for repeats lands in Form Builder

XForms has a rather powerful feature called repeats, which allows form authors to easily create forms with sets of fields that can occur multiple times. Repeats have always been supported by the XForms engine in Orbeon Forms, and now, they can also be used directly from Form Builder. For instance, consider... More

Asynchronous submissions

You might not have heard about it, but XForms supports asynchronous submissions since version 1.1. In fact, XForms 1.1 even made the asynchronous behavior the default, probably because in the browser XMLHttpRequest is asynchronous. [1] So what does it mean for an XForms submission to be asynchronous? Simply that sending the submission... More