Skip to main content

Cards: advanced features

In this chapter we describe several advanced features available in CMDBuild to consult and manage data cards. These features include:

  • searches with advanced filters
  • use of the contextual menu
  • use of scheduling
  • data import/export
  • massive modification and deletion
  • graphical display of relations (Relation Graph)
  • georeferencing of cards on geographical maps, vector maps and 3D models

Each feature is described in the following sections.

Advanced search filter​

For each card type you can apply filters to display only the cards you want to view. A dedicated funnel icon is available on the management page of each class (see paragraph 6.1).

You can select a filter among those created by the CMDB administrator and made available to operators. Alternatively, filters can be configured directly by operators in the Management Module.

Filter on attributes​

An advanced filter allows you to select data cards by applying multiple search criteria on any attribute of the current class.

In the previous example, the filter selects active employees who have a permanent contract (final date not specified) or a contract expiring after 1 January 2026.

On each filter row you can:

  • choose an attribute to which the filter condition is applied (a row for that attribute is added automatically)
  • choose an operator, depending on the attribute type
  • type a value (for strings or numbers) or choose a value (for references or lookups)
  • request the value dynamically at filter application time, for operators that allow a parametric value
  • delete a filter condition

A filter may include multiple conditions. Filters can be saved and reused later, optionally with parametric values that the operator will be asked to provide when applying the filter.

When the filter is applied, the table displays only the cards matching its conditions, and the assigned filter name is shown at the top.

Filter on relations​

Through the Relations tab you can define filter criteria based on the types of relations (domains) associated with the current class.

A relation filter allows you to extract:

  • cards that have no relations with the selected domain
  • cards that have at least one relation with the selected domain
  • cards manually chosen among those related through the selected domain
  • cards selected through a filter on the linked class, using criteria similar to those described in the previous section

In the following example, the filter selects all employees who:

  • have at least one assigned asset
  • belong to a company headquartered in Italy

Filters combining conditions on both attributes and relations can be defined and saved.

Filter on attachments​

Through the Attachments tab you can define filter criteria based on the attachments of the current class. It is possible to:

  • perform a full-text search on attachments
  • apply filters on attachment metadata

You can also save filters combining conditions on attributes, relations and attachments.

Change a filter​

The name of the active filter, if any, is displayed above the table header.

By clicking on the filter name you can:

  • apply a different filter
  • create a new filter
  • edit an existing filter
  • clone an existing filter
  • delete an existing filter
  • set a filter as the default filter for the current user when opening the class

Contextual menu​

The contextual menu, available while viewing and browsing data, provides a set of commands relevant to the current context and simplifies their selection and execution. Menu entries can be simple actions or open dedicated user interfaces.

Use of the contextual menu​

You can open the contextual menu by clicking its icon located above the column header row. It is configured in the Administration Module within class management and may include:

  • configuration and execution of views from join
  • standard functions available for all classes (enable/disable multiple selection, massive modification and massive deletion)
  • other globally available features if enabled (CSV import, CSV export, etc.)
  • custom functions applicable to the current card
  • custom functions applicable to selected cards
  • custom functions applicable to all cards displayed in the table
  • separator lines

Each contextual menu function may include:

  • a component from the CMDBuild system library, imported into the menu via the Administration Module
  • custom JavaScript code

Scheduler​

The scheduler helps operators monitor procedures related to contracts with customers and suppliers, orders, certifications, warranties, recurring operations on assets, and more. Deadlines can be generated automatically when inserting cards that include attributes marked as deadline, or they can be inserted manually into the resulting Scheduling file.
The Scheduling file can be consulted like any standard CMDBuild class, with filtering, printing, and other features.

Generation of deadlines when updating cards​

When inserting a card containing a date attribute marked as deadline, the system displays the following interface.

Since the attribute Signing date has been configured in the Administration Module to generate deadlines, an additional icon appears next to the field. By clicking this icon, you can:

  • view the list of deadlines prepared according to the defined rules
  • regenerate deadlines if the operator has modified the criteria
  • edit individual deadlines after recalculation

These edits can be useful to adjust the rounding of dates or to modify the notification prepared by the administrator.

After confirmation, deadlines are generated and added to the scheduler.
The next paragraph describes the available features for scheduling management.

Consultation and manual management of the scheduling​

The Scheduling module is a CMDBuild core feature. It may contain rows generated automatically through deadline rules or rows inserted manually.
The scheduler can be accessed through the icon in the top bar or from the dedicated entry in the navigation menu.

Inside the Scheduling page, you can:

  • add a new schedule
  • execute a quick search among available deadlines
  • configure an advanced filter
  • refresh data
  • access the contextual menu
  • switch between calendar view and grid view
  • print deadlines in PDF or CSV format
  • save grid configurations

Additional filters are also available:

  • filter by date: today, next 7 days, next 30 days
  • filter by status
  • filter by category

The Scheduling module, although a system class, inherits the standard features available to all CMDBuild classes.
You can access it in read-only mode and view all registered information.

The same information can be displayed in calendar mode.

It is also possible to update the scheduler by inserting a new deadline manually or modifying an automatically or manually inserted one.

Each deadline includes the following information:

  • Date: deadline date
  • Missing days (automatically calculated, read-only)
  • Category: deadline category (user-customizable list)
  • Priority: deadline priority (user-customizable list)
  • Description and full description
  • Participant user: if set, only this user can view the deadline
  • Participant group: if the user field is empty and the group is set, only operators in this group can view the deadline. If both are empty, the deadline is public
  • Email notification template
  • Advance notification (days)
  • Email notification text
  • Operation to execute on the deadline: changed, closed, or cancelled.
    If closed, you must specify the execution date
  • Type: deadline type (automatically generated or manually inserted)

The following widgets are also available:

  • Go to source card: opens the card that generated the deadline
  • Source card: displays the originating card according to the rules applied at save time
  • Calculation criterion: displays the parameters of the generation rule
  • Email: displays the notification text sent by the system based on the configured advance

You can also use the contextual menu to close or cancel multiple deadlines in bulk.

Views from join​

This feature allows you to configure views based on visual joins among classes, selecting attributes from each class and applying filters on extracted attributes.
These views allow data display with standard CMDBuild behaviors: text search, complex filters, contextual menu, and CSV export.

Access to features​

Configuration and consultation of join views are available from the contextual menu.

Creation of a view from join​

You can create a new join view using a dedicated wizard, divided into several steps.

Step 1 — General properties​

Required information:

  • Activity name
  • Description
  • Master class: base class for joins
  • Master class alias

Step 2 — Join definition​

You can define join modes among classes by navigating the class tree reachable through domains (1:N) starting from the master class.
For each linked class, you can define an alias and the join type (inner join or outer join).

In the example, starting from class CI, joins are defined with Company and Organizational Unit.

Step 3 — Definition of attribute groups​

You can define fieldsets to group selected class attributes in the join.

Step 4 — Attribute choice​

You can select attributes from the joined classes and make them available in the view.

Step 5 — Attribute selection​

For each attribute, you can:

  • set an alias (Description)
  • assign the attribute to a fieldset
  • choose whether to display it in the standard grid
  • choose whether to display it in the reduced grid (mobile interface)

Step 6 — Filter definition​

You can define filters on selected attributes to restrict the output of the view.
Please refer to the configuration of filters on cards.

Step 7 — Data organization​

You can define how the view will sort data by selecting attributes in sequence and choosing the order type (ascending or descending).

Consultation of a view from join​

Consultation is performed through the contextual menu.
After selecting the view, the navigation menu switches to the Views section under All elements.

Available operations:

  • perform free-text searches
  • access filter management
  • refresh data
  • access contextual menu features
  • print displayed cards (PDF or CSV)
  • save grid configurations
  • access the menu for editing or deleting a view (deletion requires confirmation)

Each record includes two tabs:

  • Card: contains the selected attributes, grouped according to configuration
  • Sources: contains the cards referenced by the record, with navigation options

Data import / export​

This feature allows you to:

  • import and sync cards and relations from files (CSV, XLS, XLSX) into CMDBuild or export cards and relations to files (CSV, XLS, XLSX)
  • import and sync cards and relations from relational database tables
  • import and sync cards and relations from DWG files (2D floor plans)
  • import and sync cards and relations from IFC files (3D BIM models)

Import and export operations are defined through specific templates, configured in the Administration Module, which include all necessary information for each type of operation.

Access to features​

Import and export features are available from the contextual menu of classes for which at least one import or export template has been configured.

../img/user/cards-advanced-features/contextual-menu.png

If templates are available, the contextual menu displays the entries Import data or Export data.
The popup lists all available templates, prefixed by the related template type.
The operator can then select the desired operation.

Import / export from files​

Import​

The feature, available in the contextual menu, opens the following popup to import data from CSV, XLS or XLSX files.

../img/user/cards-advanced-features/import-file.png

The user interface requires:

  • Template: the template used for the import (if multiple templates exist, select one)
  • File: the file to import

The operation synchronizes data in CMDBuild:

  • Merge mode: data is synchronized with existing cards
  • Add mode: imported data is added to existing cards

At the end of the import, a summary is displayed:

  • processed rows
  • new cards created
  • cards updated
  • cards deleted
  • cards unchanged
  • number of detected errors (including detailed list if present)

You can download the list of errors or send them to the email address defined in the template.

Export​

The feature, available in the contextual menu, opens the following popup to export data.

../img/user/cards-advanced-features/export-file.png

The user interface requires:

  • Template: the export template
  • Export: all cards defined by the template, or only the cards currently filtered in the grid
    (if the template contains its own filter, exporting only filtered cards is disabled)

The system exports the data into the file format configured in the template (CSV, XLS or XLSX), with headings defined in the template.

Import from relational databases​

This feature allows data import from relational database tables and is suitable for simple synchronization cases where no specific application logic is needed.
For more complex integrations, external connectors may be implemented using the CMDBuild Advanced Connector framework, which supports custom synchronization logic through Groovy scripts.

CMDBuild must be able to access a supported external DBMS (PostgreSQL, MySQL, Oracle or SQLServer).

../img/user/cards-advanced-features/database-import.png

The interface requires only the template, which includes:

  • Database: connection string and username
  • Key attribute: used to match existing cards in Merge mode
  • Missing cards behavior: how to handle records not present in the imported table (delete, update a field such as status, or ignore) in Merge mode
  • Mapping criteria: mapping between database columns and class attributes

As with file import, a summary is shown at the end:

  • processed rows
  • new cards created
  • cards updated
  • cards deleted
  • cards unchanged
  • number of detected errors (with details if any)

Import from DWG files (2D floor plans)​

This feature imports data from DWG floor plans.

../img/user/cards-advanced-features/gis-import.png

The user interface requires:

  • Template
  • File: the DWG file to import

The template, in read-only mode, shows:

  • Background objects (elements not managed in CMDBuild, such as walls, stairs or windows):
    • destination class
    • import key attribute
    • import key source
  • For each CMDBuild class updated from DWG content:
    • class name
    • source layer
    • behavior for elements missing in the DWG file

The operation synchronizes data in Merge mode, adding missing elements, updating existing ones and processing deletions according to template rules.

At the end, a summary is displayed:

  • processed rows
  • new cards created
  • cards updated
  • cards deleted
  • cards unchanged
  • number of detected errors (with details if any)

Import from IFC files (3D BIM models)​

This feature imports data from IFC files generated by BIM tools.

../img/user/cards-advanced-features/ifc-import.png

The user interface requires:

  • Template
  • Upload type: file or BIM project
  • Data source:
    • if uploading a file, select the file and the target card
    • if using a BIM project, select the project

For each CMDBuild class updated from IFC content (shown in the inclusion hierarchy), the template displays:

  • class name
  • source layer
  • import key attribute
  • behavior for elements missing in the IFC file

The operation synchronizes data in Merge mode, adding missing data, updating changed data, and processing deletions.

The final summary includes:

  • processed rows
  • new cards created
  • cards updated
  • cards deleted
  • cards unchanged
  • number of detected errors (with details if any)

Massive modification and cancellation​

The two features described below, if enabled in the Administration Module, allow you to:

  • edit one or more attributes of a set of cards selected from a class
  • delete a set of cards selected from a class

Massive modification​

This feature allows you to change the value of one or more attributes of a selected set of cards in the current class.
The function is activated from the contextual menu, after enabling multi-selection.

You can select all rows using the dedicated button or manually select only some of them.
To operate on a specific subset of cards, you can use a simple filter or an advanced filter. In this case, the select all button applies only to the filtered results.

After selecting the cards, choose the modification entry from the contextual menu.
A popup window opens, allowing you to:

  • select the attributes to edit
  • assign a new value to each selected attribute

After confirmation, the system displays the number of cards that will be modified.
A second confirmation is required to complete the operation.

Screenshots showing the steps described:

Massive cancellation​

This function allows you to delete a set of selected cards from the current class
(as always in CMDBuild, this is a logical deletion).

The steps for selecting cards are the same as those described for massive modification.
Once the cards have been chosen, select the cancellation entry from the contextual menu.

After confirmation, the system shows the number of cards that will be deleted.
A second confirmation by the operator is required to proceed.

If some of the selected cards have active relations, the system reports the issue and blocks the operation to avoid orphan relations.

To bypass this, you can configure in the Administration Module that a card may be deleted even if linked through specific relations — and that related cards are deleted automatically as well (cascade deletion).
This configuration must be used with great caution, as it applies to all CMDBuild functionalities, not only massive cancellation, and may cause unexpected data removals.

Relation graph​

This function allows you to:

  • provide a 3D visual and interactive representation of the relation graph stored in CMDBuild
  • perform interactive analysis through filters on cards and relations, graph or node expansion, and predefined filters

General design criteria of the user interface​

The user interface is divided into a text area on the left and a graphical area on the right, which are synchronized.
Two toolbars are available: one at the top and one at the bottom.

The text area includes:

  • Card tab, showing the attributes of the card selected in the graph
  • Card Relations tab, showing the list of relations of the selected card, with domain name and description of the linked card
  • Card List tab, showing all cards displayed in the graph
  • Classes tab, showing all classes represented in the graph

The graphical area includes:

  • nodes, displaying the central card and all directly or indirectly related cards up to the selected depth, using class-specific custom icons (or a default icon if none is provided)
  • edges, representing relations among nodes

Each node and edge includes a tooltip with the main information.
Selected nodes are highlighted in yellow.

Available interactions:

  • select a node (left click), updating the Card and Card Relations tabs
  • select multiple nodes (CTRL + left click)
  • expand a node (double click) to display its child nodes
  • zoom with the mouse wheel
  • move the graph (right-click drag)
  • rotate the graph in 3D (left-click drag)

Upper toolbar​

The upper toolbar allows you to:

  • reload the graph to its initial configuration
  • reload the graph centered on the currently selected node
  • apply a filter (based on a navigation tree defined in the Administration Module) to analyze a specific context

Example of filter usage:

Lower toolbar​

The lower toolbar allows you to:

  • open the graph at a higher level (useful when filters reduce visible nodes)
  • show or hide tooltips for items and links
  • show or hide labels for all items and links in the graph

On the right side, the number of nodes and edges in the graph is displayed.

Example of a graph expanded to three levels:

Text area​

The text area includes the tabs described below.

Card tab​

Shows the current card with all related attributes, grouped into fieldsets if applicable.
The card displayed here is highlighted in yellow in the graph. Selecting a different card updates the information shown.

Relations tab​

Shows the list of cards related to the selected card. For each card:

  • class name (useful when relations are defined on a superclass)
  • code
  • description

Card list tab​

Shows the complete list of cards displayed in the graph. For each card:

  • class name
  • code
  • description

Selecting a card highlights it in the graph.

Class list tab​

Shows the complete list of classes represented in the graph, with:

  • class name
  • number of cards of that class displayed in the graph

Selecting a class highlights all its cards in the graph.

Georeference on geographical maps​

CMDBuild allows you to georeference on geographical maps those entities for which a geographical attribute has been configured in the Administration Module. Geographical attributes can be point, line or polygon.
The map used by CMDBuild is based on OpenStreetMap.

You can access the map using the button located on the far right of the top bar of a class. The same button allows you to return to the list view.

The functions available on the top bar are the same as those of the card list, except:

  • when adding a new card you georeference it directly on the map
  • a new button is available to apply a thematism on the map

Tools available on the map:

  • on the left:
    • zoom in and out (you can also use the mouse wheel)
    • search for an address by opening a text box to enter and execute/cancel the search
    • show or hide the info window of georeferenced elements
  • on the bottom right:
    • set label visibility:
      • hidden
      • visible only for the selected element
      • visible for all elements of the same class
      • visible for all elements on the map
    • set the label font size

On the bottom left, the map displays the current zoom level, mouse‑pointer coordinates and the map scale.

On the right of the map is a text area that allows interaction with the card representation. It includes:

  • Navigation tree tab
  • Card list tab
  • Card tab
  • Layers tab

The navigation tree shows the hierarchy of cards georeferenced on the map, according to the structure configured in the Administration Module (GIS Navigation Tree).

The default hierarchy is: Building → Floors → Rooms → Plants / Assets.

In the GIS Navigation Tree configuration you can define the Floor entity so that, for each building, only a single floor is shown with its planimetry and all related items (people, assets, plants, etc.) georeferenced on it.

In the navigation tree you can:

  • expand or collapse tree levels
  • specify visibility of each node on the map using the checkbox
  • move the application context to the selected class and card and center the map on that element

Card list tab​

This tab displays the list of cards belonging to the current class.
The list includes all attributes for which the Display in the reduced grid flag is enabled in the Administration Module.

Card tab​

This tab displays the details of the card currently selected on the map.
It shows all attributes, grouped into fieldsets when applicable. On the top is a dedicated fieldset displaying the geographical attributes configured for that class, which you can edit directly on the map.

Available operations:

  • on the geoattribute fieldset:
    • add georeference on the map
    • edit the georeference (move point, edit line or polygon)
    • delete the georeference
    • center the map on the current geographic attribute
    • when adding or editing a geoattribute, two buttons appear to save or cancel changes
  • on the card fieldset:
    • open a popup showing the card data
    • use the dropdown toolbar to navigate directly to a specific tab of the current card

Layers tab​

This tab displays the list of layers visible on the map. They can include:

  • layers representing positions, areas or polygonal attributes (e.g. building locations, room perimeters, asset locations) managed in PostGIS
  • layers representing background vector planimetries (shape files) managed in GeoServer

Thematism​

The management of thematic maps allows you to represent information stored in cards — such as item status, duration classification, building categories or compartment types — using colors and shapes on the map.

Using the button on the top bar you can:

  • add a new thematic map (if none exists for the current class)
  • if thematic maps already exist, access the list and:
    • add a new thematic map
    • edit an existing thematic map
    • delete an existing thematic map

When adding or editing a thematic map, a popup opens where you can define:

  • Type of analysis:
    • Punctual, which assigns colors based on the value of the selected attribute
    • Interval, for numerical-attribute classification
  • Geographical attribute: the attribute on which the analysis is based
  • Source:
    • Table, to analyse a class attribute
    • Function, to use computed values from database logic
  • Attribute: the attribute from the selected source used for analysis

Once the data is defined, style rules can be generated using the corresponding button.

The thematic map can then be applied to the map or saved in the database for later reuse.

When a thematism is applied, a new tab appears on the right showing the legend and allowing you to highlight or unhighlight selected items.

Visualization of vector maps and 3D models​

From geographical maps you can access both vector planimetries of building floors (created with Autodesk AutoCAD) and 3D models of buildings (created with BIM tools such as Autodesk Revit or Graphisoft ArchiCAD).

For more information about vector planimetries and 3D models, see the following paragraphs.

Visualization of vector maps​

You can view vector maps by zooming into the area containing the planimetry.

Visualization of 3D models​

You can view 3D models by clicking the button indicating the presence of a BIM model for the selected map area.

2D georeference on planimetries​

CMDBuild manages the georeference of specific card types (rooms, plants, technical items, furniture, employees, etc.) on vector planimetries produced with design tools such as Autodesk AutoCAD.

From a card you can automatically zoom to its position on the planimetry and edit it graphically.
By navigating planimetries you can query represented items and access the corresponding card.

Planimetries can be imported using the appropriate import function described earlier.

The same features described in the previous paragraph are available when consulting and managing vector planimetries.

Georeference on 3D models​

CMDBuild also manages the georeference of its cards on 3D models imported with BIM design tools (Building Information Modeling), such as Autodesk Revit or Graphisoft ArchiCAD.
In this case an open interchange format is used, the IFC format (Industry Foundation Classes).
When a map descriptor is configured between IFC entities and the corresponding entities in the CMDBuild data model, the synchronization is performed automatically.

CMDBuild provides an interactive viewer for 3D IFC models, integrated into the standard UI. It allows you to consult the interior of a building and its assets in a realistic way. You can access the 3D viewer using the specific button available on the map.

Once activated, the viewer displays the 3D model of the selected building, as in the following example.

In the 3D viewer you can perform the following base operations:

  • use the cube to rotate the model (alternative to dragging with the left mouse button)
  • move the building model (drag with the right mouse button)
  • rotate the building model (drag with the left mouse button)
  • zoom the building model (mouse wheel)
  • use the graphic toolbar located under the graphic area

Below are the tabs included in the text area on the left.

TAB Objects​

This tab contains the IFC navigation tree, which shows the hierarchical structure of the items included in the model.

In the Objects tab you can:

  • expand or collapse levels of the tree
  • center the model on the selected element using the arrow

If you click an element of the 3D model, the corresponding element in the navigation tree is highlighted, as shown below.

At the same time the Properties tab is enabled, allowing you to view detailed information of the IFC element.
If the IFC element is associated with a CMDBuild card, the Cards tab is also enabled and displays the related CMDBuild card.

TAB Layers​

The Layers tab displays the list of item types available in the IFC model, along with the number of elements for each type.

In the Layers tab you can:

  • show or hide all items
  • show or hide only the items belonging to a specific layer using the controls on each record

If you click an element in the model, the associated layer is highlighted.

The following screenshots show an example where certain elements of the model (coverings) are made transparent:

TAB Cards​

The Cards tab allows you to consult the CMDBuild card associated with the selected IFC element.
In the example below, you can see the CMDBuild card of a monitor selected in the IFC model.

TAB Properties​

The Properties tab allows you to consult detailed information of the selected IFC element.
In the following example, the data of the IFC element related to the selected monitor is shown.

Graphic toolbar​

The toolbar located under the graphic area allows you to:

  • restore the initial visualization of the model (Reset)
  • set the default mode between Pan or Rotate
  • set the 2D view
  • set the orthogonal view
  • enable the slice option to cut through the model with an orientable plane and inspect the interior
  • remove slice effects

Below are examples of 2D view, orthogonal view and slice: