Orbeon Search

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

Configuration Properties - Form Builder

Contents

  1. 1 Default values
  2. 2 Toolbox
  3. 3 Schema types
  4. 4 Toolbox
  5. 5 Metadata
  6. 6 Roles HTTP header

Default values

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

Toolbox

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"/>


Form Builder uses the first <metadata> element found in the XBL files being loaded to display the title of the group in the toolbox.

NOTE: the following property is deprecated:

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

URI of an XBL file containing the standard components to load in Form Builder. May be missing or blank.

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]

Toolbox

<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="true"/>
<property as="xs:boolean" name="oxf.fb.menu.css"                                 value="false"/>

Whether to show various menu entries in the Form Builder toolbox.

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.

Roles HTTP header

<property as="xs:string" name="oxf.fb.security.roles-header" value="MY_HEADER"/>


This optional property specifies an HTTP header name containing a list of roles used to determine what applications and forms are visible in Form Builder's summary page.

In the header, roles can be separated by spaces, commas, or pipes ("|").

<property as="xs:string" name="oxf.fr.authentication.header.roles.property-name" value="cn"/>

Furthermore, role names within the header can optionally be composed of parts in the form of "name=value", where "name" is specified by this configuration property, and "value" is the value of the role. The reason for this logic is to support the following LDAP-related format:

cn=role1,dc=acme,dc=ch|cn=role2,dc=acme,dc=ch|...

In this example, the following list of roles is produced:

role1 role2

If oxf.fr.authentication.header.roles.property-name is left blank, then each part is directly considered a role and no parsing into name/value pairs is performed.

  Sign in   Recent Site Activity   Revision History   Terms   Report Abuse   Print page  |  Powered by Google Sites