The configuration of the individual editing fields of an editing table contains those fields which are displayed in the tool window of WebOffice 10.9 SP1 Client.


Due to a limitation in the basic technology, no information about the field length of numerical values can currently be retrieved via the REST interface. Correct input validation is not possible (e. g. 123456789 for short) and leads to an error message


Configuration of the Edit field

Configuration of the Edit field




Field alias

The field name to be used for the attribute input form

Field name

Field to be used in the attribute input form

Input field type

Specifies whether the input field in the attribute input form is to be used as the


Text input field (text input),

multiline text input field (multiline text input),

Selection value list (value list),

Checkbox (checkbox)

Slider (slider)

file name,

file path,

file upload,


is to be used.


Below you will find further information on the different input field types.


The WebOffice flex (flash) client only supports the input field types text input and value list.


Text Input:

This provides the end user a simple text field for input.  


Fields with area domains are supported by the input field type text input. The range domain is only checked for values that

a) belong to a field that is linked to an area domain,

b) belong to a field that can be edited, and

c) have been changed during the creation or editing process.

In ArcMap, an invalid value can be entered for an object if no object validation is performed. WebOffice 10.9 SP1 shows no warning if other attributes (e. g. the name of an object) are edited as attributes with domain names.

The range domain of a field is dependent on the subtype of another field (for example, feature class Street has a Speed attribute on which the range domain is dependent on the subtype of another field Street Type). WebOffice 10.9 SP1 does not show a warning if only the field Street type is changed, even though the dependent values of Speed could no longer be within a valid range.


Multiline Text Input:

This provides the end user with a text field for entering multiline values.


value list:

With this option, there are the following methods for implementing the dropdown list (arranged hierarchically, that is, methods listed first overwrite the methods below them):

Configuration of a lookup table for an edit field

Set an Esri domain/subtype to this field of the feature class or to a subtype (note that you configure the same hierarchical level for the editing fields as that resulting from domains and subtypes, i. e. the field for the domain must be one hierarchy level lower)

Configuration of Values for the Selection Value List

Configuration of the individual values for the dropdown list as edit fields


The available lookup values can be limited by entering specific existing field values in the Selection value list edit field parameter. Afterwards, only these lookup values are read out in the editing form. However, this method only works for lookup values, not for subtypes/domains.



This option saves integer values (0=not checked, 1=checked) in the attribute field



Use the slider for numerical values, especially for rotations


The slider is only supported by the WebOffice core client, in all other clients this is replaced by a text input field.

If you want to use a slider, make sure the Format Definition parameter is correctly configured.


File Name, File Path, File Upload

This option opens a file dialog in the client to specify a file path. For all three fields, the attribute field must be of the field type Text (string).

file name: only the filename is saved

file path: saves the entire path


Important: The file path option sends the entire path to the server in IE, in all other browsers only the file name.

file upload: saves the file name together with a timestamp. Use this option to upload a file to a configured path.


In the chapter Edit Attributes you will find further information about the input field types in WebOffice core Client.

Mandatory field?

Determines whether a value must be entered in the input field so that the edited object can be saved.

Hierarchical level

Defines the level of the hierarchical input field, e. g. 1 top level, 2 next level below, etc.


If the maximum number of list values is exceeded on a hierarchical input field, all input fields that are hierarchically dependent on it remain grayed out. It is either possible to increase the maximum value or to completely forgo the functionality of the hierarchical levels in this field.

Note the use of hierarchy levels when using domains on subtypes. If a domain is configured on a subtype (e. g. subtype color green, domain color light green, dark green), then the Color field must have hierarchy level 1 and the Hue field must have hierarchy level 2. The field with hierarchy level 1 must be configured as a mandatory field so that no unnecessary selection list is provided on the field with hierarchy level 2 if nothing has been selected in the first field.

Drop down list

Allows you to set allowed selection list values for the input field directly in the project configuration. Individual values are separated by |, e. g. 3 selection values Green space, Building land and Industrial area can be configured as follows: Green space|Building land|Commercial area.


The specified values must match the field data type, e.g. if the field data type is Long Integer, a|b|c cannot be configured as a selection list.

If you use lookups for the edit field, you can restrict the values of the selection value list. Use here the lookup ID to set a value list. If a value cannot be found in the lookup table, it is not displayed on the client.

If an Esri domain or subtype is defined for the field, this configuration value is ignored.


Determines how to sort in selection lists. Sorting according to the field type fieldtype is possible as well as specifying a special alphanumeric sort order alfanumeric for fields of the data type String (character strings) with partly numerical contents such as real estate, parcel and house numbers.

Input validation

Determines the type of input validation if the input field type is textbox:

URL (A URL of the form must be entered),

filename (A filename of the form xxxx. xyz must be entered. Special characters prohibited in file names are not allowed),

email (An email address of the form must be entered),

format (entry must be made according to the format definition).

Input format

You can generate a format character for user input: \n for number \c for letters, e. g. \n\n\n\n\n\n for a four-digit postcode.


An empty entry in the field means that the format is not checked. Administrators should inform their users about the format by configuring an appropriate example in the alias field. With WebOffice 10.9 SP1 the defined format is no longer displayed in the client.

When using the input field type slider, the formatting should be defined as follows:

Minimum Value|Maximum Value|Interval|Card Preview (true, false)|Rotation Style (arithmetic[Default], geographic]|Additional Guideline (true, false[Default]).

Example: 0|360|10|true|geographic creates a slider from 0 to 360 with 10 steps. Additionally there is a map preview and the rotation style is geographic.


For more information, see chapter Edit Attributes.

The following regular expressions are available: \. \* \+ \/ \? \$ \^ \| \ (\) \c \n    

Please note that the configured format definition is not taken into account as soon as the edit field also has a selection value list. This automatically converts the input field type from text input to value list.

Default value

Allows you to define a specific field value as the default value in the input form. Use the following variables to use dynamic default values:

{date} for an edit field of type date inserts the current date as default value.

{user} for an edit field of type string inserts the currently logged in user as default value. If no user is logged in because WebOffice usermanagement is deactivated, the user name Anonymous is entered.

{display_name} corresponds to the name of the logged on user or anonymous if no user is logged in.


Please note that the variable {display_name} must not be set on an audit field ( CREATE_BY, CHANGE_BY).

{client_id} for an edit field of type string inserts the client identifier of WebOffice usermanagement group of the currently logged on user as default value. If WebOffice usermanagement is deactivated, the field remains empty.


No default value may be configured when using editing templates.

Reuse the last input value?

Should the value assigned during the last data entry process be proposed?


This attribute makes it easier to edit multiple objects of the same type. As long as the editing form is activated, the last input for the next object is reused, even if the layer is changed. All entries are only deleted when the editing form is closed.

Show field?

Determines whether the field is displayed in the edit form (Yes) or not (No). The configuration value No makes sense if the field is used, for example, as a key for linking to another database. This can be useful, for example, if the field entry is passed on to an integrated external Web application (see chapter Integrated Editing Application).

Property Edit Field



The display of the editing fields can also be categorized as a Group of Editing Fields.

See Chapter Edit Table for information on configuring the editing table.

See Chapter Edit Table (ArcGIS Feature Service) for details to edit tables in WebOffice core client: