Field attributes

The labels can be internationalized.

Opens a dialog for Rights manager.

Directly opens the editing mask to change field attributes.

By clicking on the button, the meta data from the data model is exported to an Excel file and directly opened on the client computer.

An explanation of the individual fields is additionally included in the Excel file as the “Key” spreadsheet.

The old export directory (System Preferences) will no longer be needed

Figure: Exported metadata in an Excel file

At this point, you can filter according to entities and configuration groups.

The font can only be changed in the cluster. The font size must be set to the default size of 12 so that the font size from the user preferences can be considered. Italic, bold and bold italic can be selected as the font format. All system font types are available as font types. Even though the list only shows set font sizes, individual values can be entered as well. The font setting can be removed using the X in the field attribute dialog, so that the default is restored.

The respective unit can then be entered under Layout. After the settings for the field properties have been exited, the unit in the desired field is highlighted in gray.

The background is only available for normal text, number, date and suggestion fields, whereby only the key is stored in color here. This option is not available for the memo fields and checkboxes. If a field is invalid and declared as a required field, the standard color red will be displayed. The background color can be removed via the X in the field attribute dialog, so that the default color is restored.

This field attribute is not available for labels.

The configuration groups specific settings for lookup fields were also activated for text fields (RecordableRegexFormattedTextField). This option is deactivated by default (activated for lookup fields). The option has a direct effect on field values so that the text is saved in the database in upper case letters. If the field should explicitly show upper case letters (match code with RecordableUpperCaseRegexFormattedTextField), the option will not be shown, because it has no effect.

The thickness of the field frame can be selected from 0 pixels (no frame) to 5 pixels in a drop-down list. The default value is 1 pixel.

If this option is activated, this lookup field will only accept number values.

Hint

Configure the number fields for the input of up to 15 numbers.

With this button the description part of the lookup field can be displayed or hidden.

The display of the key field can be controlled via the checkbox. This procedure is similar to the existing functionality for hiding the description field. The application ensures that at least the key or the description field is always visible, i.e. both fields cannot be simultaneously hidden. This is achieved by the check being automatically placed by Show lookup description field when deactivating the Show lookup key field checkbox (and vice versa).

If the key field is hidden, the button to open the lookup browser becomes focused, this means when changing the focus using the ↔ Tab, this also stops on the button. This ensures that the application can always be operated via the keyboard.

When activated, the “Key part” takes over all available space.

If checked the key is shown in the tabular view and in the navigator view.

Prerequisite: the “Show in list” field (groups configuration) is activated.

If checked the description is shown in the tabular view and in the navigator view.

Prerequisite: the “Show in list” field (groups configuration) is activated.

In the detail view, the symbols of keys are displayed.
If no symbol has been stored for a key, a white circle is displayed.

In the list view, the symbols of keys are displayed.
If no symbol has been stored for a key, a white circle is displayed.

Decides on the visibility of the field.

You can reach the internationalization dialog via the button next to it. In this dialog, the tooltip text can be entered for multiple languages for the currently selected field or text. The new “tooltip” field attribute including the internationalization will be considered during the import/export of the customizing.

1. The tooltip is not available for fields based on the HTML editor (for example, the “Description” field in the activity).

2. The content of the condition is displayed as a tool tip in the search mask.

The horizontal alignment of the content can be changed for normal text and number fields. The standard alignment for text fields is align left and align right for number fields. You can choose between left, right and centered. The empty line can be selected in the drop down list for the default value.

Toggle the visibility of the time component

If this field is marked, the search field will be filled in default searches for the entity and can be used to restrict the search. To fill the standard search dialog from an independently created entity with fields, the corresponding fields must have the search field attribute.

When processing a search, all fields from the search can be added as a condition independent of whether or not this field is marked.

The fields that are marked as search result fields each represent a column in the table from the search mask that contains the search results quantity.

When this field is selected, the field content to identify datasets will appear in the tree layout or in the Levels menu.

This field specifies in which order the field content is listed in the tree layout or in the menu point levels. If several values are specified, these are illustrated separately with commas.

This can be used to block the field for the user independent of the concrete conditions of a dataset. If the option is deactivated, the “normal” rights concept applies; if it is activated, the field will be shown read-only.

Specifies that the value can only be written when creating a new dataset.

Specifies, whether the field is readable.

The corresponding field is displayed in a quick entry mask, provided that such a mask exists (for example, for business partners and contact persons)

If this field is checked, the field will be assigned a default value from the configuration when creating a new dataset.

The default value can be entered for a new creation of a dataset here.

The behavior:

• In fields that are not text-based, the corresponding input field is available in the dialog for field attributes. Patterns cannot be used in these fields. Individually, these fields are of the type

  • Yes/No

  • Memo field

  • Lookup field

  • NMemofield

  • Key field

  • Number

• In text-based fields, a modal dialog opens to enter the standard value. The user can choose between two input options with the checkbox

  • Checkbox deactivated: Input of the default value via the basic input field

  • Checkbox activated: Input of the pattern in an open text input field. Only the regular expression #PATTERN#[.*] must be fulfilled for the text field, for example: #PATTERN#[NUMBER6].

• text-based fields include:

  • Text

  • NText

• In date fields, a modal dialog opens to enter the default value analog to the text fields. The user can choose between two input options with the checkbox

  • Checkbox deactivated: Entry of a fixed date value as a default value via the basic date field

  • Checkbox activated: TODAY is defined as a default value here and cannot be changed by the user. Following the new creation, the current date is used as the default value.

• If the customizing transport is active and the customizing is not allowed, the default value may not be changed.

Deactivating the “Set default value” flag does not result in the automatic emptying of the “default value” field.

Using the dialog for configuring the default values, the problem with a limited number of font properties in a field can be bypassed.

Example: if a maximum of 10 font properties is allowed for a field, you can use a pattern that exceeds 10 characters.

Formal: #PATTERN#[ Pattern $!!$ Pattern]

A pattern is the string 'Pattern' and not the whole expression.

In that case:

#PATTERN#[<15font properties>$!!$<15font properties>]

The 15 font properties in the code refer to the "key", which is referred to here as the pattern.

Pattern

Patterns only work for string fields.

1. Patterns may have at most 15 characters.

Syntax: #PATTERN#[ Pattern $!!$ Pattern]

Informative specification: Indicates the size of the table column in the database. This value cannot be modified.

An entry in this field makes the field mandatory for the user so that a valid value must be entered. This setting is global, because such an entry is required for all users for data consistency.

Important technical fields that are not declared as mandatory fields because they should be filled in, but cannot always be filled in. A percentage fill level of this important information is calculated from the filled information, which can be evaluated.

further information about →Data quality

If this field property is set or removed, the Lucene index of the affected entity must be rebuilt so that the data quality display is updated for all datasets in the affected area.

A regular expression that describes the valid input values for the field can be entered in the input mask field. For a complete description of regular expressions, we refer to the Oracle documentation. Furthermore, a defined string can be entered that implies a certain field behavior.

Customized descriptions that should correlate with the input mask and the input example (see input example) can be included in the error message for the field.

The input mask usage example is intended as a message text in the event of incorrect entries. In connection with an error message, the form Error, field format, valid example is used.

Specifies, whether this lookup field should automatically be filled from a superordinate sentence during a new creation (for example, an activity below a project).

The selected fields are exported to Excel instead of the lookup field. If no field is selected, the lookup field will be illustrated as in the list view.

Optionally indicates the lookup key field. The user selects the field from all search input fields in the lookup search. If no field is selected, the first field of the lookup search is used.

Defines the fields from the lookup search to be displayed in the tooltip. Hereby the order of the fields can also be defined.

Defines the fields from the lookup search to be displayed in the description text of the lookup field. The configuration applies equally to the detail view and the list view. Hereby the order of the fields can also be defined.

Specifies, whether this is a not persistent lookup field. Values of these fields are only determined by searching. The field content itself is not stored in the database table.

Indicates, whether this is a picklist field. Here the user can make free inputs, e.g. for the street name. The property is defined when a lookup field is created.

Only the key is displayed in picklist fields. This applies if the "Key only", "Description only" and "Key + Description" options have been selected for the "Field content in detail masks" system setting.

Indicates the entity that is being looked up.

Configuration of the search restrictions used for preselection and the proposal list. Each configuration is stored in a new row.

In a syntax with <field name>[.<function>]=<value>[-[AllIfEmpty][Pk]] the defined <value> is used as a pre-filter, whereby as value either a fixed constant or the value of another field (mask or AttributeContainer) with {field name.entity name} can be referenced.
Example: ItemtypeKey.Product[.EQUAL]={ItemtypeKey.OpportunityItem}[-[AllIfEmpty][Pk]]

In the example a function is specified optionally, with which the given value is checked. If no function is specified, NONE is used. The standard function is then automatically used when looking up or validating (user preferences). The following functions are possible:

• NONE (Default)

• EQUAL

• UNEQUAL

• LIKE

The AllIfEmpty suffix indicates that if the default value for "ItemtypeKey.OpportunityItem" is empty, all key values are looked up:
ItemtypeKey.Product={ItemtypeKey.OpportunityItem-AllIfEmpty}
The Pk suffix is used to control that the primary key of a lookup field is transferred to the preselection instead of the key value:
Pk.Customer={CustomerKey.Customer-Pk}
A combination of AllIfEmpty and Pk is possible:
Pk.Customer={CustomerKey.Customer-AllIfEmptyPk}

Here the lookup search is configured, which is used when looking up and validating lookup fields. The default search follows the naming convention "LookupEntity<entity name>". The following rules must be observed for lookup searches:

1. When creating a lookup search, the existing C0 search should always only be extended

2. No fields may be removed

3. The key field should be the 1st field of the search, but this can be overridden using the field property "Lookup key field".

4. The Dataset Status field may not be checked. Inactive datasets are filtered separately.

5. The PK field must be included as a search result field

6. Restrictions of the result set should be implemented using preselection fields or mask script.

Specifies, whether the input should be validated.

No validation will be done if the field attribute is deactivated. There is no suggestion list (except for 'apply') and the field value is applied directly when the field is left with the ↹ TAB or ENTER ↵ key.

Configuration of the search restrictions used for preselection and the proposal list. See "Lookup preselection fields" for more details.

Indicates, whether this is a numeric lookup field.

Set whether the search will be case sensitive.

This property decides if the field is already obtained during the initial loading of a dataset or first in the second step. Changes to this property should only be individual cases and on agreement.

Since different masks can be selected for input on the fields, the Java object that performs the filter function can be determined here. If, for example, a text field should be converted into a lookup field, there does not have to be an implementation, but rather merely an adjustment to the mask field.

Specifies, whether this field should be included in the Juhuuu index.

A “calculated field” is read-only in the client. The field value is read during an update to the dataset and not again from the database. The value can be calculated e.g. via a database function in a selection.

A value that is displayed in a field that is not marked as a “calculated field” via the database function will no longer be visible when changing to the detail view, because the value at this time is read from the database.

Displays the field in the Workflow Creator

Changes to fields can be logged. All changes (per field) are saved in the “ChangeHistory” table with a comment. The history of field changes can be enabled as a CURSOR module. If the history of field changes is active, you can store a commentary field for the update. The comment field itself is not logged, but rather only contains the additional information when the actual field is changed.

A small corner in the top right is shown in the field if history is active. It can only be viewed with the function right show.change.history.permission. Only the administrator may do this by default. The dialog to view the history can be opened via the field’s context menu (also in list view).

As the values (new value and old value) are saved in the database as BLOB and the data type of a field may change, no meaningful sorting and filtering can be done in the table. The display is only manipulated in each row so that valid values are displayed.

The field is saved here (if active) and acts as a comment field.

Previously, it was possible to copy (duplicate) a dataset (activity, project, request, offer, contract) via the button. As a result, the user received a 1:1 duplicated dataset with the same fields. If the Unique Field attribute is activated, the field will be emptied in the copy.

In the C2 layer, a double value in a field whose default value is set via pattern can be prevented during copying.

This setting determines if a message will be displayed with duplicate field values.

Defines whether a field contains confidential information.

You have to deactivate the option to make a field writable for the app.

Determines whether a field is made anonymous. By default, all fields are made anonymous. Assumed are fields like Primary key, Create user/date or Update user/date. Also, lookup fields are not anonymized because a primary key is stored in the database. The property cannot be set on these fields.

Pattern

Description

NUMBERx

#NO#x

Creates an x-digit number for the current entity.

#NO# can also be used instead of the NUMBER pattern

NUMBERKEY(key)x

#NO#KEY(key)x

Creates an x-digit number for the current entity and the key.

#SER#x

Creates an x-digit sequential, gapless number for the current entity.

Using these variants may lead to wait states or errors when requesting the number on other clients, because this is determined within a transaction and is also rolled back again when the transaction fails.

#SER#KEY(key)x

Creates an x-digit sequential, gapless number for the current entity and the key.

Using these variants may lead to wait states or errors when requesting the number on other clients, because this is determined within a transaction and is also rolled back again when the transaction fails.

#SYSTEMNO#x

Creates an system-wide x-digit number. The client assignment of the user is ignored.
(only with activated client module)

#SYSTEMNO#KEY(key)x

Creates an system-wide x-digit number for the key. The client assignment of the user is ignored.
(only with activated client module)

#SYSTEMSER#x

Creates a system-wide, continuous, x-digit number. The client assignment of the user is ignored.
Using these variants may lead to wait states or errors when requesting the number on other clients, because this is determined within a transaction and is also rolled back again when the transaction fails.
(only with activated client module)

#SYSTEMSER#KEY(key)x

Creates a system-wide, continuous, x-digit number for the key. The client assignment of the user is ignored.
Using these variants may lead to wait states or errors when requesting the number on other clients, because this is determined within a transaction and is also rolled back again when the transaction fails.
(only with activated client module)

DATE

Date in the format dd.MM.yyyy

{YYYY}

Year four digits

{YY}

Year double digit

{MM}

Month double digit

{M}

Month

{DD}

Day double digits

{D}

Day

VALUE–<Field name>[(x,y) |

#<Field name>]

The value of a text field or lookup field from the same entity. It may not be calculated. The internal field name must be specified without entity. Parts of the field value can be cut out via the numerical values x and y. The numbers must be in single digits. The java.lang.String.substring() logic is used here.
If the field is a lookup field, a field from the lookup entity can be used.

PK

Creates a unique primary key. If the dataset already has a Pk, this is used, otherwise a new one is generated. The primary key is converted to uppercase if the field allows only capital letters.

LAYER

The current layer. Values: C0, C1 or C2.

PARTNERID

The partner ID for customizings in the C1 layer, e.g. C11. Otherwise empty.

000001

000001

#PATTERN#[#SYSTEMNO#6]

(only with activated client module)

000001

0001

#PATTERN#[#SYSTEMSER#4]

(only with activated client module)

0001

Number: 000002

Number: 000003 on 07.08.2007

Number: 000004 2.Number 001

Number: 000005 Your inquiry...

Number: 000006 CP SHORT NAME

creates a 6-digit number for the value in Freetext1. The name of the entity is added to the beginning of the value.