Custom Forms

With Imixs-Office-Workflow you can create forms completely model-based. No programming knowledge in HTML or Java Script is required. The custom form component enables you to design your forms at runtime. The definition of a custom form is done within the Imixs-BPMN modeler. To activate this feature you need to add the from “custom” into the section “Application -> Input Form” of your task element.


The definition of your custom form is defined by a “Data Object Element” with an association to your task element:

The Form Definition

The XML definition contains sections and items:

<?xml version="1.0"?>
  <imixs-form-section label="Controlling">
    <item name="description" type="textarea"
        label="Short Description" />
    <item name="details" type="html" label="Description" />

The following common input formats are supported:

Text Input

<item name="description" type="text"
        label="Topic" />

Textarea Input

<item name="description" type="textarea"
        label="Description" />

HTML/RichText Input

<item name="description" type="html"
        label="Description" />

Date Input

<item name="" type="date"
        label="Date" />

Select Boxes

You can also create different type of select boxes with predefined values:

 <item name="invoice.currency" type="selectOneMenu" 
	options="EUR;CHF;SEK;NOK;GBP;USD" />

You can choose one of the following types for select boxes:

Required Inputs

With the tag ‘required’ a mandatory input is defined:

<item name="_date" type="date" required="true"
        label="Date" />

Form Sections

A custom form is separated by sections. A section can have an optional label and up to 3 columns:

 <imixs-form-section label="Controlling" columns="2">

Custom Input Fields

It is also possible to define more complex input fields with the item type ‘custom’

    <item name="mycustomitem" path="[PART_NAME]" type="custom" label="My Custom Label" required="true" readonly="false" />

Note: A custom item is defined by a JSF ui:composition placed in the directory /pages/workitems/parts/:


The mandatory path attribute contains the path for JSF component relative to the /pages/workitems/parts/ directory with the .xhtml extension. You can also use sub directories to group custom input items.


See the following example of a custom input field definition:

<ui:composition xmlns=""
	<span class="custom-class"> 
	   <h:inputText style="border:2px solid blue;" 
	                a:placeholder="enter custom data..." 
	                rendered="#{!readonly}" />
	    <h:outputText style="border:2px solid blue;" 
	                rendered="#{readonly}" />

Note: This custom input form uses also the attributes ‘readonly’ and ‘required’ to determine if the input component is editable or readonly.

Custom Input Section

As an alternative to the custom input fields you can also define custom sections. A custom section defines a complete form section and is used for more complex input forms including ajax.

  <imixs-form-section label="My Custom section" path="sub_custom_form" > 

Note: A custom section is defined by a JSF ui:composition placed in the directory:


See the following example of a custom input field definition:

<ui:composition xmlns=""
	<!-- show outgoing references -->
	<div class="imixs-form-section">
			<dt class="imixs-no-print">
				<h:outputText value="#{message['form.reference.outgoing']}" />
				<marty:workitemLink workitem="#{workitem}" readonly="#{readonly}" 
					filter="" />

Note: Also in a custom section you can use the attribute ‘readonly’ to determine if the input components are editable or readonly.