Map

The map element allows you to list started processes on the dashboard. For each process, you must specify either coordinates or an address where the process should be displayed on the map. For example, you can show various incidents, targets for resource planning, and similar items.

info

In an on-premise environment, you must connect a map service to use this element.

Configuration

The following options are available within the configuration:

• Title:
  Enter the display name of the element here. This will be displayed to users so they know which control it is.

• Selected Processes:
  Here you must select the process types to be displayed on the map. For example, you can insert an Incident Report process if you plan to display accidents on a map.

• Location:
  In this section, you define the location where the placeholders are displayed. You have the following options per selected process:

  • Format:
    Use the format to determine whether you want to define the location using latitude and longitude or an address.
    Note: If you are working in an on-premise environment, you must have connected a GeoCode service to use an address.
  • Latitude:
    Here you must specify the latitude at which the marker for the respective process will be displayed. This value could, for example, be loaded from a map in a form.
  • Longitude:
    Here you must specify the longitude at which the marker for the respective process will be displayed.
  • Address:
    Determine the address where the marker will be displayed here. If there are multiple matches for this address, the first result is used.

• Data Value:
  Data values are displayed when clicking on a marker. This allows you to show specific values directly from a form, for example. These values can also be used for filters or color rules (see below). After inserting a data value via the corresponding button, the following options are available to you:

  • Data Value Name:
    This value is displayed to the users and helps them identify what kind of data it is.
  • Value per Process:
    Using a placeholder, you can determine here for each selected process which values are used for this data value. This can be, for example, a form value, a process value, or a process variable.

  Using the pencil icon, you can make the following additional settings per data value:

  • Hide Data Value:
    If this option is enabled, the data value is not displayed to the users, but it can still be used for filters or color rules, for example.

• Filter:
  If you do not specify a filter, users will see all processes to which they have access. However, if you only want to display specific processes (such as processes started by the logged-in user, or only processes in a specific status), you can insert filters. Multiple filters are linked with an AND condition, meaning a process must meet all filter conditions to be displayed.
  Per filter, you have the following configuration options:

  • Select Column:
    Here you select the data value used for the filter.
  • Select Operator:
    Select the comparison operator for the filter here.
  • Comparison Value:
    Define the comparison value here. You can manually enter fixed values or reference another value using a placeholder.
    If you want to allow multiple values, you can separate them with |.

  For example, if you have created a column with the process status as a data value, you can define this status as the column, not equal as the operator, and Approved|Rejected as the comparison value to show only processes that have not yet been approved or rejected.

• Marker Colors:
  Here you can determine the colors in which the markers are displayed. For instance, you can display problematic processes in red, while showing other markers in green. This allows users to see at a glance which points they should focus on. To implement this, you can configure the following points:

  • Default Color:
    Here you can select the default color per process.
  • Color Rules:
    Using color rules, you can use a different color depending on the state of a process. If multiple color rules apply to a marker, the last rule is used. You can define the following values per color rule:
    • Target Color:
      Here you select the color that will be used for the marker if the condition for the rule is met.
    • Select Column:
      Here you select the data value that is used for the condition.
    • Select Operator:
      Select the comparison operator for the filter here.
    • Comparison Value:
      Define the comparison value here. You can manually enter fixed values or reference another value using a placeholder.
      If you want to allow multiple values, you can separate them with |.

• Geodata:
  In this section, you can link geodata to the map. This allows you to show areas of responsibility on the map, for example.
  You have the following configuration options per level:

  • Geodata:
    Select the geodata entry here that will be inserted into the map.
  • Visibility:
    Here you can determine if and when this geodata is displayed on the map. If Visible by default or Hidden by default is selected, users can change the visibility later in the dashboard.

• View:
  Here you can influence how the map is displayed on the dashboard. You can set the following values for this:

  • Map:
    If more than one map is available in the system (e.g., a map of Germany and a map of France), you can select the map here.
    Note: Since a world map is available in the cloud, you cannot switch between maps here and therefore do not have this option available.
  • Height:
    Here you can set the vertical height of the map on the dashboard.
  • Default View / Markers:
    This option opens a map. You can then focus on the area that should be displayed by default. This could be, for example, a specific city or a wooded area.