brainX

Layout

Package: BASIC

1. General

Info

The term "layout" refers to the presentation of a record in the detail view, i.e. the display and positioning of fields and blocks.

A layout additionally defines which actions are available and which fields are shown when displaying and selecting records.

Layouts can be adapted to the needs and processes of users and groups in order to present records more clearly, which in turn promotes a more efficient way of working.

In the "Layout" tab, all settings for layouts (detail view of a record) are managed. Existing layouts can be edited and new layouts can be created.

2. Layouts overview

In the "Layout" tab, all existing layouts are displayed as tiles.

modulverwaltung_tab_layout_monitor.pngModule management - "Layout" tab

Each tile (layout) provides the following functionalities:

modulverwaltung_tab_layout_kachel_aktionen.pngTile of a layout with action icons

3. Create layout

To create a new layout, either the "Create layout" button or the "Plus" action icon in an "empty" tile must be clicked.

The creation view of a new layout is divided into two areas:

modulverwaltung_tab_layout_neues_layout_erstellen_monitor.pngCreation view of a new layout

Note

In order to be able to edit the blocks and fields of a new layout, it must be saved at least once.

Layouts can be set to active directly upon creation.

3.1. Basic settings

In the basic settings, the name of the layout is defined.

Using the "Default view" checkbox, you can specify whether the layout should be displayed as the default view for all users.

Note

Each user can - despite the "Default view" setting - individually specify which layout they want to use as the default view.

3.2. Assign roles

Roles can optionally be assigned to a layout. The layout is then only available to users who belong to these roles.
If no role has been assigned, the layout is available to all users.

3.3. Configure layout

Once a new layout has been saved for the first time, the configuration of blocks and fields can now take place.

The "Standard" layout serves as the basis for the new layout.

modulverwaltung_tab_layout_neues_layout_gespeichert.pngModule management - Configure layout

The further configuration of blocks and fields is identical to that described in the section Edit layout.

4. Edit layout

After clicking the "Edit" action icon ("pencil" icon) in the tile of a layout, the "Layout" tab opens in the editing mode of a layout.

modulverwaltung_tab_layout_kachel_aktion_bearbeiten.pngAction Edit layout

In the "Layout" tab, in the blocks and fields area, the following configurations/actions can be carried out:

Note

The actions within a block in the "Layout" tab are only displayed on mouseover of a block.

modulverwaltung_tab_layout_block_alle_aktionen.pngExample: Layout tab - Block actions

4.1. Basic settings

In the basic settings, the name of the layout is defined.

Using the "Default view" checkbox, you can specify whether the layout should be displayed as the default view for all users.

Note

Each user can - despite the "Default view" setting - individually specify which layout they want to use as the default view.

4.1.1. Assign roles

Roles can optionally be assigned to a layout. The layout is then only available to users who belong to these roles.
If no role has been assigned, the layout is available to all users.

If roles are added/removed, the layout is accordingly available or no longer available for certain users/roles.

4.2. Blocks

Info

The term "block" refers to the - usually thematic - grouping of fields within an area bounded by a frame.

4.2.1. Add block

To add a new block, two options are available:

  • "Add block" button → opens the "Add block" popup
  • "Plus" action icon (is only displayed on mouseover of the area between two blocks) → opens the "Add block" popup

The "Add block" popup provides the following fields:

  • Block name (DE German) → name of the block
  • Block name (further languages) → translations of the block name into other languages
  • Insert after → picklist with the already existing blocks
  • Number of columns → picklist to set the value for the number of columns (values: Dynamic, 2-6 columns)
  • Display status → picklist to define the display status of the block (values: expanded, collapsed and hidden)

modulverwaltung_tab_layout_popup_block_hinzufuegen.png"Add block" popup

After clicking the "Save" button, the new block is created and displayed. In the next step, custom fields can now be added.

4.2.2. Arrange blocks

To arrange a block, two options are available:

  • Action icon "Arrange blocks" ("four arrows" icon) → opens the "Arrange blocks" popup, in which the blocks can be repositioned using drag & drop
  • Action icons (in the top right corner of each block)
    • "move up" ("pointed arrow up" icon) → moves the block up one position with each click
    • "move down" ("pointed arrow down" icon) → moves the block down one position with each click

modulverwaltung_tab_layout_aktionen_icon_bloecke_anordnen.pngAction icon "Arrange blocks"

modulverwaltung_tab_layout_popup_bloecke_anordnen.png"Arrange blocks" popup

4.2.3. Delete block

Note

The actions within a block are only displayed on mouseover of a block.

modulverwaltung_tab_layout_block_aktion_block_loeschen.pngAction icon "Delete block"

After clicking the "Delete block" action icon ("Recycle Bin" icon), a popup appears with the query "Do you really want to delete the block?".
After clicking the "Confirm" button, the block is deleted.

Note

Only blocks that no longer contain any fields can be deleted!

If an attempt is made to delete a block that still contains fields, a corresponding notice is displayed. The popup shows which layouts are affected.

modulverwaltung_tab_layout_block_loeschen_popup_loeschen_nicht_möglich.png"Deleting block not possible" popup

4.2.4. Edit block

Note

The actions within a block are only displayed on mouseover of a block.

modulverwaltung_tab_layout_block_aktion_block_bearbeiten.pngAction icon "Edit block"

After clicking the "Edit block" action icon ("pencil" icon), the "Edit block" popup opens.

modulverwaltung_tab_layout_popup_block_bearbeiten.png"Edit block" popup

The "Edit block" popup provides the following fields:

  • Block name (DE German) → name of the block
  • Block name (further languages) → translations of the block name into other languages
  • Number of columns → picklist to set the value for the number of columns (values: Dynamic, 2-6 columns)
  • Display status → picklist to define the display status of the block (values: expanded, collapsed and hidden)
    If a block contains mandatory fields, the block cannot be hidden.

4.2.5. Expand/collapse

Note

The actions within a block are only displayed on mouseover of a block.

modulverwaltung_tab_layout_block_aktion_block_ein_ausklappen.pngAction icon "Expand/collapse block"

By clicking the "Expand/collapse block" action icon ("chevron up/down" icon), a block can be expanded or collapsed.

Note

Expanding and collapsing in the layout management is used exclusively to improve clarity when editing the layout in the Global Settings, and has no influence on the presentation in the detail view. The actual initial state of a block in the detail view, as well as in the editing view, is defined exclusively via the block editing.

4.3. Fields

4.3.1. Hidden fields

Note

The actions within a block are only displayed on mouseover of a block.

Note

Fields can be deactivated in the settings of a field ("Active" checkbox). Deactivated fields then count as "hidden".

If a block contains hidden fields, the "hidden fields" action icon ("crossed-out eye" icon) is available.

modulverwaltung_tab_layout_block_aktion_verborgene_felder.pngAction icon "hidden fields"

After clicking the "hidden fields" action icon ("crossed-out eye" icon), the "Hidden fields" popup opens.

modulverwaltung_tab_layout_popup_verborgene_felder.pngHidden fields popup

The popup lists all hidden fields. Using the checkbox, the fields to be shown can be selected and shown again using the "Show selected" button.

4.3.2. Add custom field

Note

The actions within a block are only displayed on mouseover of a block.

modulverwaltung_tab_layout_block_aktion_benutzerdefiniertes_feld_hinzufuegen.pngAction icon "Add custom field"

After clicking the "Add custom field" action icon ("Plus" icon), the "Add custom field" popup opens.

modulverwaltung_tab_layout_popup_benutzerdefiniertes_feld_hinzufuegen.png"Add custom field" popup

The popup is divided into two areas:

4.3.2.1. Basic settings
4.3.2.1.1. Properties

The field type is defined using the "Type" picklist. For certain field types, further configuration options for the field are available, which are automatically displayed after selecting the field.

The following field types are available for selection:

  • Text → standard text field
    • further configuration options: length (max. number of characters)
  • Number → field for entering numbers
    • further configuration options: length (max. number of characters), decimal places (number of decimal places)
  • Percent → field for entering percentage values
    • further configuration options: none
  • Currency → field for entering amounts
    • further configuration options: none
  • Date → date field
    • further configuration options: format (Date, Date and time as well as Time), current time as preselection (if the checkbox is ticked, the field is pre-filled with the current time)
  • Email → field for entering email addresses (checked for correct syntax on entry/save and displayed as a hyperlink)
    • further configuration options: none
  • Phone → field for entering phone numbers (displayed as a hyperlink if a telephony connection has been configured in the PBX Manager)
    • further configuration options: none
  • Fax → field for entering fax numbers (displayed as a hyperlink if a telephony connection has been configured in the PBX Manager)
    • further configuration options: none
  • Picklist → field for selecting predefined picklist values → see Note on picklist values
    • further configuration options: creation of new values allowed (if the checkbox is ticked, users with the corresponding profile permission can create new values in this picklist)
    • additional configuration options: Variable mandatory fields and Picklist dependencies → see Note on picklist
  • Reference → existing records can be selected from other modules, thereby establishing references (links) to other modules
    • further configuration options: target modules (selection of one or more target modules), default (default for selecting a record, only displayed when multiple target modules are selected)
  • URL → field for entering URLs/web addresses (displayed as a hyperlink)
    • further configuration options: none
  • Checkbox → field of type checkbox/toggle
    • further configuration options: none
  • Text area → field for entering multi-line text
    • further configuration options: width (narrow/wide), HTML formatting (if the checkbox is ticked, a toolbar for formatting the text is displayed)
    • additional configuration options (with HTML formatting enabled): default font, default font size
      They define the font or font size with which a new record is pre-filled in this field. The available values are taken from the editor configuration and are automatically extended as soon as further languages or font sizes are added there.
  • Multi-selection box → field for selecting multiple predefined picklist values → see Note on picklist values
    • further configuration options: creation of new values allowed (if the checkbox is ticked, users with the corresponding profile permission can create new values in this picklist)
    • additional configuration options: Variable mandatory fields → see Note on picklist
  • File → upload field for uploading files into the brainX system
    • further configuration options: width (narrow/wide), file types (selection of the allowed file types, no selection means all file types are allowed), multiple upload (uploading multiple files is allowed)
  • User selection → field for selecting all (active) users
    • further configuration option: none

Note on picklist values

For a picklist (field type "Picklist" and "Multi-selection box"), multiple field values can be entered during creation in the "Values of the picklist" area. When a new field value is entered, a further input field automatically opens.

modulverwaltung_tab_layout_popup_benutzerdefiniertes_feld_hinzufuegen_werte_der_auswahlliste_farbe.png"Add custom field" popup - Values of the picklist

In the input field for the name of a picklist value, a "colour picker" is available, with which a colour can be defined for the picklist value.

If the column of the picklist is displayed in a list view of a module, the field value is highlighted in the list view according to the selected colour.
This provides a very good visual overview in list views.

Note on picklist

For the field types "Picklist" and "Multi-selection box", further tabs for configuration are available in the "Add custom field" popup:

  • "Variable mandatory fields" tab (field types "Picklist" and "Multi-selection box")
  • "Picklist dependencies" tab (field type "Picklist")

"Variable mandatory fields" tab

Note

Before configuration is possible, at least one picklist value must exist.

The "Variable mandatory fields" setting item offers the option of defining selected fields as mandatory depending on a picklist value.

modulverwaltung_tab_layout_popup_benutzerdefiniertes_feld_hinzufuegen_variable_pflichtfelder.png"Add custom field" popup - "Variable mandatory fields" tab

If a picklist value has been selected in the "Selection of the list value" area, an overview of all fields that can be defined as mandatory fields is displayed in the lower "Selection of the mandatory fields" area.

Using the checkbox at each field in the "Selection of the mandatory fields" area, it is now defined which fields are mandatory when the corresponding picklist value is selected in the creation or editing mode of a record.

Note

Variable mandatory fields are set directly on the target field and can - analogous to the Automations - be combined with condition groups.

  • Any field of the module can serve as a condition, no longer only picklists.
  • During mass editing, variable mandatory fields are checked per record.
  • Existing settings were automatically adopted during the update.
Warning

Fields to which a corresponding function of the variable mandatory fields is applied can no longer be edited via the Quick Edit and mass editing function.

Warning

If a picklist value is deleted in the layout management, all mandatory field configurations linked to it are irrevocably removed.

Warning

[CSV imports]() and [CSV updates]() – which contain fields or picklist values for which variable mandatory fields have been defined – are executed without a corresponding check!

"Picklist dependencies" tab

Note

Before configuration is possible, at least one picklist value must exist.

In the "Picklist dependencies" tab, you can define which picklist values are available in other picklists when a certain picklist value has been selected in the picklist.

modulverwaltung_tab_layout_popup_benutzerdefiniertes_feld_hinzufuegen_auswahllistenabhaengigkeiten.png"Add custom field" popup - "Picklist dependencies" tab

Warning

At least one entry per column must be selected in the target field, otherwise the dependency cannot be created.

If a picklist dependency is configured, the source and target field are no longer available for the Quick Edit function. These fields can therefore not be edited individually, neither in the [list view]() nor in the [detail view](). The picklists can only be changed in the editing mode of a record.

Warning

Picklist dependencies only take effect in the editing mode of a record and not when [background tasks]() or [Automations]() are executed!

"Field value transfer" tab

Note

The "Field value transfer" tab is only available in the Leads module.

Info

Using the "Convert lead" action in the [Leads]() module, a record can be converted. Converting means the lead record is deleted and a new record is automatically created in the [Contacts]() module. Optionally, records can additionally be created in the [Organizations](), [Partner](), [Deals](), [Appointments]() and [Tasks]() modules.

Custom fields that are to be taken into account during conversion can be configured in the "Add custom field - Field value transfer tab" popup.

modulverwaltung_layout_modul_leads_feld_anlegen_uebergabe_feldwerte.pngAdd custom field popup - Field value transfer tab

In the "Field value transfer" tab, you define into which modules the data from this field should be transferred during lead conversion. Only fields of a suitable type that are not already configured for other fields are permitted here.

For the four modules

  • Module: Organizations
  • Module: Contacts
  • Module: Partner
  • Module: Deals

it can be defined separately for each whether and into which target field the field value should be transferred during conversion. In each of the four picklists, in addition to the existing fields of the respective target module, the following default values are also available for selection:

  • Do not transfer → The field value is not transferred into the target module during conversion.
  • Create field and transfer → A new field with an identical field type and name is automatically created in the target module and the field value is transferred there. The new field is inserted into the default block of the default view of the respective target module.
4.3.2.1.2. Name

In the "Name" area, the display name of the field is defined in multiple languages in the "Name" field.

4.3.2.1.3. Default value

In the "Default value" area, it is possible for predefined field types to assign a default value. This means that when creating a record, the field is pre-filled with this value.

4.3.2.1.4. Create help text

Optionally, a so-called "help text" can be created for fields. If a help text has been configured, the "i" icon is displayed at the field in the editing view of a record.
On mouseover of the icon, the help text is displayed.

After clicking the "Help text" button, a text area is displayed in which the help text can be entered in multiple languages.

Tip

A help text is helpful for many users if the field name alone is not descriptive enough and can then provide the users with completion guidance.

Short instructions or general notes about the field are also helpful for many users.

4.3.2.2. Settings

In the "Add custom field" popup, the "Settings" area is displayed on the right-hand side, in which additional configurations for a field are available.

4.3.2.2.1. Mandatory field

Mandatory fields are marked in the creation and editing view of a record with a red asterisk * .

A record cannot be saved if there is no valid value in a mandatory field!

Note

If there is a picklist dependency between two fields of type picklist, the target field of this picklist dependency cannot be defined as a mandatory field!

4.3.2.2.2. Mass update

In list views of modules, the Mass edit action is available.

If the "Mass update" setting has been activated, the field is also available accordingly in mass editing.

4.3.2.2.3. Quick create

At various places in the brainX system, new records can be created using the so-called "Quick create" (e.g. the "Create" action in the navigation bar). This means that only a popup window with the most important fields is displayed, instead of the creation view of a new record.

If the "Quick create" setting has been activated, the field is also available accordingly in the popup window.

4.3.2.2.4. Additional information

If the "Additional information" setting has been activated, the field is not available in the main mask for data entry but is displayed in a separate sidebar in the detail view of a record.
The button for showing and hiding the "Additional information" sidebar is displayed permanently in the detail and editing view - regardless of whether the mouse pointer is over the area. Using this button, the "Additional information" setting for the respective field can also be deactivated directly.

modulverwaltung_seitenleiste_zusaetzliche_angaben_beispiel_detailansicht.pngDetail view - "Additional information" sidebar

In addition to the fields themselves, the name of the [block](/en/global-settings/module-management/layout#4.2.-blocks) in which the field is located is also displayed.

The "Additional information" setting is suitable for fields that

Note

The "Organization-related" setting item is only displayed in the Contacts module.

In addition to a main organization, further organizations can be referenced for a contact in the "Organization" reference field. If a different organization is selected in the detail view of a record in the Contacts module, the record is reloaded. The respective organization-related values of these fields are then displayed. The values of the "organization-related data" therefore have a direct dependency on the selected organization.

On the one hand, there are fields already marked as organization-related by default by the brainX system; on the other hand, new custom fields can also be marked as "organization-related" when creating them in the module manager.

Note

Organization-related fields can be moved into any block in the "Module management - Layout" setting item and do not necessarily have to be located in the "Organization-related data" block.

However, it is recommended to place the organization-related fields in the "Organization-related data" block, as there is no visual marking for organization-related fields. If a different organization is selected in the organization-related field "Organization", the page is reloaded and the organization-related fields have a different value or possibly no value anymore. This can lead to confusion if one or more organization-related fields are in a different block, since the change of the field values may happen unnoticed.

4.3.2.2.6. Audit-proof
Note

The "Audit-proof" setting item is only displayed in the Products and Services modules.

Info

Audit-proof fields are necessary in order to comply with legal requirements, prevent manipulation, ensure transparency and create legal certainty.

Warning

Audit-proof fields cannot be deleted.

Audit-proof fields can be used in PDF templates within the position groups.

4.3.2.2.7. Active languages
Note

The "Active languages" setting item is only displayed in the Products and Services modules.

Warning

As soon as a multilingual field exists, the default language of the system can no longer be changed!

In addition to the default language, further languages can be activated here for the custom field.

4.3.3. Delete field

Note

The actions of a field are only displayed on mouseover of the field.

modulverwaltung_tab_layout_feld_aktion_loeschen.pngAction icon "Delete field"

After clicking the "Delete field" action icon, a popup appears with the query "Do you really want to delete?".
After clicking the "Confirm" button, the field is deleted.

Note

When deleting a field, a notice may appear that the field cannot be deleted because it is still in use. The notice informs about the specific places of use, e.g. in an automation, a report or a list view. The field can only be deleted after it has been removed from all listed places.

In some cases, it may additionally be necessary to also delete records from the Recycle Bin module before a field can finally be deleted. This concerns fields that were used in records that have already been deleted but not yet permanently removed from the Recycle Bin.

Note

The fields available upon delivery of the system can be adapted differently in the layout depending on the field type. Fields that are not needed can be deleted from the layout, deactivated via the field properties ("Active" checkbox) or hidden by adjusting the display status of a block.

If certain user groups are to have different fields or field arrangements available, a new layout can be created for this and assigned to the corresponding role.

Whether a field can be deleted, deactivated or hidden depends on the respective field type as well as on whether the field is defined as a mandatory field on the system side.

4.3.4. Edit properties

Note

The actions of a field are only displayed on mouseover of the field.

modulverwaltung_tab_layout_feld_aktion_eigenschaften_bearbeiten.pngAction icon "Edit properties"

After clicking the "Edit properties" action icon ("pencil" icon), the "Edit properties" popup opens.

4.3.4.1. Basic settings tab
modulverwaltung_tab_layout_felder_popup_eigenschaften_bearbeiten.png

In the "Edit properties" popup, exactly the same functionalities are available as when creating a custom field.

The exception here is the "Type" field and the length of a field, which can no longer be changed afterwards.

In the "Edit properties" popup, the same options are available as when creating a custom field - with the exception that the Type and the length of a field can no longer be changed afterwards.

4.3.4.2. Field value transfer tab
Note

The "Field value transfer" tab in the "Edit properties" popup is only available in the Leads module!

Info

Using the "Convert lead" action in the [Leads]() module, a record can be "converted". Converting means the lead record is deleted and a new record is automatically created in the [Contacts]() module.

Optionally, records can additionally be created in the [Organizations](), [Partner](), [Deals](), [Appointments]() and [Tasks]() modules.

In the "Field value transfer" tab, you define into which modules the data from this field should be transferred during lead conversion. Only fields of a suitable type that are not already configured for other fields are permitted here.

modulverwaltung_tab_layout_felder_popup_eigenschaften_bearbeiten_uebergabe_feldwerte.pngEdit properties popup - Field value transfer tab (Leads module)

In the four picklists

  • Module: Organizations
  • Module: Contacts
  • Module: Partner
  • Module: Deals

it is defined whether the field values should generally be transferred, or into which fields the field values are transferred upon transfer.

4.3.5. Move field

Fields can be moved both within a block and into other blocks using drag & drop.

Using the "Configure links" action, the modules that are displayed in the detail view of a record in the Relations tab in the respective layout are configured.

modulverwaltung_tab_layout_kachel_aktion_verknuepfungen_konfigurieren.pngAction icon "Configure links"

After clicking the "Configure links" action icon ("chain links" icon) in the tile of a layout, the "Configure links" popup window opens.

modulverwaltung_popup_verknuepfungen_konfigurieren.pngConfigure links popup

Using the toggle, you can now configure which modules should be displayed.

The order of the modules, as they are displayed in the "Relations" tab, can be defined using drag & drop.

After clicking an "Advanced configuration" action icon ("chevron" icon), the area expands so that further configurations can be made.

modulverwaltung_layout_popup_verknuepfungen_konfigurieren_block_ausgeklappt.pngConfigure links popup - Advanced configuration

The following configuration items are available:

  • Configure columns → configuration of the columns that are displayed for the module. The fields can be sorted using drag & drop. With the "Add field" button, further fields can be selected for display. To remove a field, the "Remove field" action icon ("x" icon) of the respective field must be clicked.
  • "Action after record creation" field (picklist) → If the "create record (module name)" action icon is clicked at a module in the "Relations" tab, a new record can be created for the module concerned. In the "Action after record creation" field, it is configured what happens after the new record is created:
    • To the source record → After creating the new record, the record in which the action was started is called up again.
    • To the new record → After creating the new record, the newly created record is displayed.

6. Edit actions

Using the "Edit actions" action, the actions that are displayed in the flyout menu in the detail view of a record after clicking the "Actions" button are configured.

modulverwaltung_tab_layout_kachel_aktion_aktionen_bearbeiten.pngAction icon "Edit actions"

modulverwaltung_aktionen_bearbeiten_beispiel_detailansicht.pngDetail view with flyout menu of the actions

After clicking the "Edit actions" action icon ("two arrows with dot" icon), the "Edit actions" popup opens.

modulverwaltung_popup_aktionen_bearbeiten.png"Edit actions" popup

The popup displays all existing actions in a four-column list view:

  • Action → icon and name of the action
  • Field mappings → number of existing field mappings
  • Status - display of the status (active/inactive) in the form of a toggle to set the status of the action (active/inactive)
  • Actions → "three dots" action icon to display a flyout menu with further actions for the respective action (whether and which actions are displayed depends on the respective action and the module concerned.)

modulverwaltung_popup_aktionen_bearbeiten_aktionen_flyout_menue.png"Edit actions" popup - Flyout menu with actions

Using the actions in the flyout menu, actions can be edited, copied or deleted. Whether and which actions are displayed depends on the respective action and the module concerned.

Note

Actions with the status "inactive" are still available in Automations!

New action

Using the "New action" button, new actions can be added. After clicking the "New action" button, the "New action" popup opens.

modulverwaltung_popup_aktionen_bearbeiten_neue_aktion.png"New action" popup

The following fields are available here for configuration:

  • View → name of the layout for which the action is created (display only)
  • Copy into view → selection of further layouts/views into which the action should be copied
  • DE German → selection of the icon (see screenshot ""New action" popup - Select icon" below) and input field for the name of the action in German
  • Languages → input field to enter the translation of the name in further languages
  • Transfer module → selection of the transfer module (the creation view in this module is opened)
  • Target view → selection of the layout that should be opened in the transfer module

modulverwaltung_popup_aktionen_bearbeiten_neue_aktion_icon_auswaehlen.png"New action" popup - Select icon

7. Copy layout

Using the "Copy layout" action, complete layouts can be copied in order to create new layouts that are very similar to the current layout.

modulverwaltung_tab_layout_kachel_aktion_kopieren.png

After clicking the "Copy layout" action icon ("two sheets" icon), the "Copy view" popup opens.

modulverwaltung_popup_ansicht_kopieren.png"Copy view" popup

The following settings can be adopted:

  • Roles → assigned roles are adopted
  • Field arrangement → the existing field arrangement is adopted
  • Actions → all configured actions are adopted
  • Dashboard → configuration settings of the dashboard are adopted

After clicking the "Save" button, the editing view of the copied layout is displayed for further configuration.
All the functionalities described in the section Edit layout are available.

8. Edit actions in the header area

Using the "Edit actions in the header area" action, the action icons displayed in the header area in the detail view can be configured.

modulverwaltung_tab_layout_kachel_aktionen_aktionen_im_kopfbereich_bearbeiten.png

modulverwaltung_aktionen_im_kopfbereich_beispiel_detailansicht.pngDetail view - Actions in the header area

After clicking the "Edit actions in the header area" action icon ("arrow up" icon), the "Edit actions in the header area" popup opens.

modulverwaltung_popup_aktionen_im_kopfbereich_bearbeiten.png"Actions in the header area" popup

The "Edit actions in the header area" popup is divided into two columns:

  • Available → selection of the action that should be displayed in the header area (limit = 4 actions), the selection is made by clicking the action
  • Selected → display of the selected actions
    • Actions can be sorted using drag & drop
    • On mouseover of an action, the "x" action icon is displayed, with which the action can be removed from the column of selected actions.
      Using the "Empty list" button, all actions in the "Selected" column are removed.

9. Layout active/inactive

Using the "Active/Not active" toggle, it is configured whether the layout is generally active/not active.

modulverwaltung_tab_layout_kachel_aktionen_schalter_aktiv.png
Note

Inactive layouts are no longer available to users when selecting a layout.

10. Delete layout

Using the "Delete" action, the complete layout can be deleted.

modulverwaltung_tab_layout_kachel_aktionen_aktion_loeschen.png

After clicking the "Delete" action icon ("trash can" icon), a popup appears with the query "Do you really want to delete the view "view-name"?"

After clicking the "Confirm" button, the layout is permanently deleted.

Warning

Deleted layouts are permanently deleted and cannot be restored!

11. Practical examples

1 – Create a role-specific layout for Sales

The sales team is to receive a clear presentation with the most important fields in the detail view of Deals, while accounting needs an extended view with payment and invoice fields. In the module manager of the Deals module, a new layout Sales is created via Create layout and assigned to the role Sales employee. Fields such as purchase price and margin are removed from the layout. A second layout Accounting receives all financial fields and is assigned to the role Accounting.

2 – Create a new custom field "Priority" with picklist and colours

In the Deals module, a new field Priority with the values High, Medium and Low is to be added, which are highlighted in colour in the list view. In the layout editor, an existing block is extended via the Plus action icon. In the Add custom field popup, the type Picklist is selected. The three values are entered and each provided with a colour (High = Red, Medium = Orange, Low = Green). The field is activated as Mass update so that it can also be changed from the list view.

3 – Adapt an existing layout by copying

An existing layout Standard is to serve as the basis for a new layout Field service that has fewer fields and a simplified structure. Using the Copy layout action icon on the Standard tile, the Copy view popup is opened. Field arrangement and Actions are adopted. In the copied layout, blocks that are not needed are emptied and deleted, and the role Sales field service is assigned.

4 – Adapt links in the Relations tab

In the Contacts module, the modules Deals and Tasks are to appear at the very top in the Relations tab and the Delivery Notes module is to be hidden. Using the Configure links action icon, the popup is opened. The toggle for Delivery Notes is deactivated. Deals and Tasks are dragged to the top positions using drag & drop.

12. Frequently asked questions

Can a module have multiple layouts at the same time?

Yes. Any number of layouts can be created per module. Each user can switch between the layouts available to them in the detail view via the view selection. If a role is assigned to a layout, only users of this role see it.

Why does a user see a different layout than expected?

The displayed layout depends on which layout the user has chosen as the default view and which layouts are enabled for their role. Even if a layout is marked as the system-wide default view, each user can individually set a different layout as their personal default.

Why can't a block be deleted?

A block can only be deleted if it no longer contains any fields. All fields must first be moved to other blocks or removed from the layout.

What happens to data when a custom field is deleted?

All data values stored in this field are irrevocably lost. Before deleting, brainX checks whether the field is still used in automations, reports or list views, and provides a corresponding notice. The field can only be deleted after being removed from all listed places.

Can I change the field type of an existing field afterwards?

No. The type and length of a field cannot be changed after creation. If a different field type is needed, the old field must be deleted and a new field with the desired type must be created.

What is the difference between "deactivating" a field and "deleting a field from the layout"?

Deactivating (removing the Active checkbox) hides the field without losing the stored data – the field counts as hidden and can be shown again at any time. Deleting removes the field permanently, including all stored data values.