This is an internal documentation. There is a good chance you’re looking for something else. See Disclaimer.


Entities can be displayed in various views. Forms definitions determine how these views are arranged.

There is an old and a newer form-model. The later was introduced to fit the new client’s needs. This chapter describes attributes and tags that are valid for the new form-model. Most of them will also work for the old one though. Those that are exclusively for the new form model are marked with a V2

Types and naming

As of today there are five different types of forms:




To display multiple entities of the same kind in a list.


To display one entity. This can either be a read-only or writable views.


Special view to create an entity. If not defined, detail view is used as fallback.


Special view to update an entity. If not defined, detail view is used as fallback.


Optional search form that gets embedded above a list form.

The forms are defined as an xml file in the following location: <module-root>/resources/model/forms

A form file has following naming schema: {Name, PascalCase}_{Type}.xml

To create an entities default view, {Name} is substituted with the entity name. Entity names are written as they are and not in PascalCase. If a form is created for a flow {Name} is usually substituted with the flows name.

Examples: Event_category_detail.xml, RegistrationAdministration_list.xml

Auto Forms

If there is no xml definition for an entity form a list, detail and search form is generated automatically. This happens during the runtime and the form will not be persisted in a xml file. The generated form simply contains all fields of the entity.

List Forms

Simple Example:

<?xml version="1.0" encoding="UTF-8"?>
<form xmlns="">
  <table data="User">
    <field data="firstname"/>
    <field data="lastname"/>
    <column sortable="false">
      <field data="email"/>


data (String)

Name of the entity that should be listed.


constriction (String)

Listed entities are filtered with this constriction. (A constriction is like a filter but is defined as ConstrictionContribution)

sorting (String)

List of fields separated by comma. This sorts the records in ascending order by default. If a descending order is needed a minus sign (-) can be prepended to the field name.

Example: sorting="firstname,-lastname,"

If not specified the entities default sorting will be applied.

selectable (null, false)

If not set, selectable is dynamically determined. If the main action bar contains an action it’s true. If true, the rows are always selectable (even if there is no action). If false, the rows are never selectable (even if there are actions). This feature is needed if there are actions or reports that should be triggered for selected records.


data (String)

Path to field. Fields related with a n to 1 relation can also be visualized using dots and the relations name.


<multi-remote-field> and <remote-field>

constriction (String)

Constrictions can be added to remote-fields and multi-remote-fields.

<multi-remote-field data="relRoom" constriction="active_rooms"/>

The active_rooms constriction must then also be registered as a bean in the module configuration.

public ConstrictionContribution roomSearchFiltersConstrictionContribution() {
    return new ConstrictionContribution("active_rooms", "active == true");


To make constrictions for remote-fields and multi-remote-fields also work in the old admin, you need to provide the field with a form.

<multi-remote-field data="relRoom" form="reservation" constriction="active_rooms"/>

Since the field in the example shows Rooms and the form is called “reservation”, we also need to create a file called Room_reservation.xml. The content of that file contains the table that will be shown in the old admin as the dropdown list of the remote-field. This table can be now be pre-filtered by providing the same constriction as for the new admin:

<?xml version="1.0" encoding="UTF-8"?>
<form xmlns="">
  <table data="Room" constriction="active_rooms">


A Column is used as a wrapper to add special attributes.


The name is used to retrieve the corresponding text-resource or reference a position.

display-type (String; editable, readonly, hidden)

Determines how the field is displayed. If hidden, the label is also not shown. At the moment, editable is not regarded in the context of list views.

sortable (true, false)

Whether there is an arrow shown in the column that let the user sort the table accordingly.

sticky (false, false)

True for sticky column (display specific columns at all times while the user scrolls the table horizontally)

Detail, Search, Create & Update Forms

Simple Example:

<?xml version="1.0" encoding="UTF-8"?>
<form xmlns="">

<horizontal-box labeled="false">
  <vertical-box labeled="false">
    <vertical-box name="user_information" labeled="true">
      <field data="firstname"/>
      <field data="lastname"/>
      <field data="email"/>
    <vertical-box name="marketing_information" labeled="true">
      <field data="relAffiliation" scopes="update,read"/>


<horizontal-box>, <vertical-box>

Boxes for layouting purposes. Search forms do not support any layouting boxes.

labeled (true, false)

If a layouting box is labeled the name tag is required. The textresource is getting resolved with the following path: forms.{form_name}.{boxes}.{name} {boxes} is substituted with all named boxes on a higher level (eg. box1.box1_subbox…)

label (String)

The default text resource path can be overwritten with a custom path.

name (String)

Only needed if labeled is true and label is not set.


data (String)

Same as in list form data (String)


Same as the display-type used for a column. See display-type (String; editable, readonly, hidden)

use-label (String, yes, no, hide)

If yes a special form text-resources is looked up: forms.{formName}.{boxes}.{fieldName}

If not defined the entities field text-resource is used.

For more information about text-resources see Text-Resources

label (String)

Overwrite the default text-resource path.

scopes (String; read, update, create)

Selectively show field. For example if the scope of a field is set to update, the create view will not show it.



Is used to embed freemarker expressions into the form.

<display name="relDebitor.balance_open" language="freemarker" escape-html="false">

The escape-html attribute allows you to define if html is escaped in the resulting text. The compressible attribute allows you to define if whitespace should be compressed in the resulting text.

<table> V2

A table in a detail form is called a sub-table. Its used to list to n relations. The id of the table is either the name given to it, the form-suffix attribute or the data attribute, in that order.

<horizontal-box labeled="false">
  <table data="relIncoming_payment" show-search-form="false" limit="25"/>

data (String)

Name of the relation that should be shown in the sub-table. This can be also be a relation path over multiple steps, like relRating.relExam.

name (String)

Is used to set an id on the sub-table.

form-suffix (String)

Can be used to use a custom form for the table. By default, the data attribute is used.

endpoint (String)

By default, the list view retrieves its data from the default entities endpoint. With this attribute its possible to overwrite this default behavior. A GET request is sent to the endpoint. If your endpoint does not resolve a relation directly, be sure to set the data attribute of the table to the entity model that you are returning. If used in a sub-table, the {parentKey} placeholder can be used.

Usually you will want to build your endpoint similiar to EntitiesResource, but replace the query or filter the results in some way.

Full example with custom endpoint that loads independent Registration entities
<table data="Registration" endpoint="custom/registrations/{parentKey}"/>

show-search-form (true, false)

Whether a search form is displayed or not.

limit (Int)

How many records to show on one page. If not defined usually the REST default of 25 is shown.

Form composition

A form can be changed by any module that extends the module containing the form. Special attributes help to position additional components. The order of the composition is depending on the module dependencies. For more information see Importing Modules

Example that adds the field relConstricted_business_unit to the Event_category_detail form

<?xml version="1.0" encoding="UTF-8"?>
<form xmlns="">

<horizontal-box name="box1" labeled="false">
  <vertical-box name="box1" labeled="false">
    <vertical-box name="master_data" labeled="true">
      <field data="relConstricted_business_unit" position="after:sorting"/>


position (String; top,bottom,*middle*,before,after)

The position of a component can be applied to <field> or <column>.

before and after need a relative position such as a field name appended.

position="after:firstname" position="before:firstname"


To remove components, a special file with the following naming convention has to be created: remove{formName}.xml`


<?xml version="1.0" encoding="UTF-8"?>
  <remove xmlns="">
  <form name="User_detail">
    <component path="box1.box2.employee_information.relEmployment"/>

Actions V2

See Form possibilities