Configuration Properties - Form Builder

Site map

Comments? Feedback?

This wiki does not yet support public comments (a limitation of Google Sites), so we encourage you to post your comments either:

On Twitter by responding to @orbeon.

On our community mailing list: subscribe sending an email to ops-users-subscribe@ow2.org (content of subject/body doesn't matter), you'll get a response with the email to use to send your message to the community mailing list.

Recent site activity

Orbeon Forms 3.9.1 PE
edited by Erik Bruchez
TinyMCE Editor
edited by Alessandro Vernet
attachment from Alessandro Vernet
XForms - Attribute Value Templates
edited by Erik Bruchez
XForms - Actions
edited by Erik Bruchez
Implementation Notes - XForms Engine Static XPath Dependency Analysis
edited by Erik Bruchez
View All

Documentation‎ > ‎II. Developer and Administrator Guide‎ > ‎Configuration Properties‎ > ‎

Configuration Properties - Form Builder

Contents

1 Default values
2 Toolbox
1. 2.1 Control groups
2. 2.2 Toolbox top-level entries
3 Schema types
4 Metadata
5 Maximum number of columns
6 Access control

Default values

For the latest configuration, see properties-form-builder.xml.

Toolbox

Control groups

You configure the contents of the toolbox by configuring properties of the form:

<property as="xs:string" name="oxf.fb.toolbox.[GROUP].text.uri.*.*" value="[URI LIST]"/>

In that property, the value of the group determines a grouping of the controls in the toolbox. The controls are defined by a list of XBL files. For example:

<property as="xs:string" name="oxf.fb.toolbox.group.text.uri.*.*"
                         value="oxf:/forms/orbeon/builder/xbl/text-controls.xbl
                                oxf:/xbl/orbeon/inplace-input/inplace-input.xbl"/>

To properly show up in the toolbox, XBL files need to include the appropriate group metadata and control metadata.

Toolbox top-level entries

In addition to controls, the toolbox shows other "menu entries", which you can enable or disable with the following properties:

<property as="xs:boolean" name="oxf.fb.menu.schema"       value="true"/>
<property as="xs:boolean" name="oxf.fb.menu.pdf"          value="true"/>
<property as="xs:boolean" name="oxf.fb.menu.edit-source" value="true"/>
<property as="xs:boolean" name="oxf.fb.menu.view-source" value="false"/>
<property as="xs:boolean" name="oxf.fb.menu.css"          value="false"/>

Schema types

<property as="xs:anyURI" name="oxf.fb.schema.uri.*.*" value="oxf:/forms/orbeon/builder/standard.xsd"/>

URI of an XML Schema file containing the standard schema types to load in Form Builder. May be missing or blank. [NOTE: NOT IMPLEMENTED YET]

Metadata

<property as="xs:boolean" name="oxf.fb.metadata.logo" value="true"/>

Whether to allow uploading a custom logo image. If set to false, this is not allowed and the default logo, if any, is used.

Maximum number of columns

<property as="xs:integer" name="oxf.fb.grid.max-columns" value="4"/>

[SINCE 2011-05-20] Use this property to change the default maximum number of grid columns form authors can create. The more columns there are, the more narrow each column is, and when columns become too narrow, some less "elastic" controls might not have enough space to render properly. You want to set this property to a "reasonable" value to reduce the chance of form authors ending up with columns that are too narrow to accommodate certain controls.

Access control

If you'd like to have multiple classes of Form Builder users where some case edit, say, form in the hr app, while other can edit forms in the sales app, see Access to specific apps/forms in Form Builder.

	Orbeon Search