Top.Mail.Ru
Sphere of Processes
CTRL+K

Sphere of Processes

In this article
  • Sphere of Processes
  • Widget Settings
  • Data Settings
  • Display Settings
  • Filtering Settings
  • Browse Mode
  • Click-to-Filter
  • Widget Configuration in YAML
  • Data Settings in YAML
  • Display Settings in YAML
  • Filtering Settings in YAML
  • Example of a Configured Widget in the YAML Editor
Note

A Business User (Process) or Analyst (Process) license is required to use this feature.

The Sphere of Processes is functionally equivalent to the Process Explorer. The key difference is that the sphere allows you to visualize multiple processes within a single chart.

Sphere of Processes example

Widget Settings

In addition to the common widget settings, this widget has unique options.

Data Settings

Process Settings

To add a process, click the + Process button and select the desired one from the dropdown list.

By default, when a process is added, the first 80% of its events are displayed. To adjust the number of displayed events, click the process and then the settings icon.

Configuring the number of displayed processes

In the modal window that appears, use the slider to set the percentage of events—the number of selected events updates automatically.

You can also manually select events by checking the corresponding boxes. Use the search field to find a specific event.

Click Save to confirm or Cancel to discard changes.

Event selection

Additionally, clicking a process in this section allows you to set its color on the widget:

  • Auto (default; cannot be customized)
  • Solid (color selected from the palette)
  • By rule (only rules with base mode are available)

Changing process color

Note

You can add metrics only after selecting a process. The widget supports event and transition indicators. Adding a custom indicator locks the field and prevents switching processes. Removing the indicator unlocks the process selection again.

Event and Transition Indicators

After selecting a process, the widget automatically creates the following default indicators:

  • Event indicators: Number of events and Number of overtimes (can be added manually via + Indicator)
  • Transition indicators: Number of transitions and Median time

These default indicators are optional and can be deleted.

Event and transition indicators

Important

You cannot add a standard measure based on a Data Model column to a transition indicator—doing so will result in an error in the widget.

Indicator Formulas

Formulas for event indicators may include:

  • The CaseId column and related columns (aggregated/non-aggregated/no function)
  • Columns other than CaseId and unrelated to CaseId (aggregated functions only)
  • Calculated variables (aggregated/non-aggregated/no function)
  • Constants (aggregated/non-aggregated/no function). Function type depends on context. Constants can be used without aggregation.

Formulas for transition indicators may include:

  • Columns other than CaseId and unrelated to CaseId (aggregated functions only)
  • Calculated variables (aggregated/non-aggregated/no function)
  • Constants (aggregated/non-aggregated/no function)

Standard metrics for each process use different formulas due to variations in table and column names.

Indicator Settings

Beyond the standard measure settings, additional options are available for default indicators.

For Number of events and Number of overtimes, you can:

  • Show numeric values in event blocks
  • Adjust the size of the dot to the left of the number
  • Set the Display condition (Always / By variable / By formula)

For Number of transitions and median time, you can:

  • Show numeric values in event blocks
  • Adjust transition arrow thickness
  • Set a range (Number of transitions only; default: 1–8)
  • Set the Display condition (Always / By variable / By formula)

You can also add event and transition click actions and specify a widget key.

Note

You can define up to 2 transition indicators.

Number of Overtimes

Number of overtimes is calculated using the following formula:

count() - uniqExact(case.case_id)

This computes the difference between the total number of event executions and the number of unique case IDs—yielding the number of repeated executions per event.

Median Time

Median time is calculated as:

medianExact(date_diff(second, begin(event.Time), end(event.Time)))

This returns the median duration (in seconds) between the start and end of an event. You can later apply a desired duration format in the widget.

Display Settings

In addition to the common display settings, you can adjust the text size and indicator (numeric) size.

Filtering Settings

Beyond the standard filtering settings, you can configure an Event filter.

Event Filter

To add an event filter, click + Event filter. A menu appears with the following parameter sources:

  • Custom (opens the formula editor)
  • Dashboard (shows dimensions created in the dashboard)
  • Workspace Common group (shows workspace-level dimensions)
  • Tables (shows columns)

Filter parameter options

After selecting an option, a window appears where you can choose values from dimensions or columns and apply filters. The available filter types depend on the data type of the selected dimension or column.

Selecting a predefined filter

Note

A filter configured in the widget cannot be removed in Browse mode. If the Dashboard and/or Common groups contain no dimensions, they are not displayed.

Browse Mode

In Browse mode, you can customize the sphere’s appearance. The top-left corner of the widget contains the following buttons:

  • Open in full-screen modal window
  • Reset zoom to 100%
  • Zoom out
  • Zoom in

A configuration panel showing processes and events appears when you click the icon in the top-right corner. You can hide any item by clicking its name or the eye icon.

Sphere of Processes view

Events hidden in Browse mode are appended to the dashboard’s URL.

A slider on the right side of the widget controls the number of displayed transitions. Below the slider is a process selector button to choose which process’s transitions to adjust.

Sphere of Processes view

Note
  • To maintain browser performance, process instances with 100 or more events are excluded from the sphere calculation and not displayed.
  • Only events selected in edit mode appear in Browse mode. If no events were selected, the published widget appears empty.
  • The number of displayed transitions is capped at 500.

Click-to-Filter

In Browse mode, you can interactively apply filters by clicking elements:

  1. Click an event block.
  2. Then click the flag icon (event filter) or the arrows icon (Number of overtimes filter).

When two event blocks are selected, additional icons appear:

Transition duration and existence filters

Selecting any filter opens a configuration window. Click Apply to filter the data.

Filter window

You can add additional filters for events by clicking the + Filter button.

Event Filter

Select an event and process, then choose a filter type:

  • Initial — shows processes where the selected event is first
  • Not initial — shows processes where the selected event is not first
  • Final — shows processes where the selected event is last
  • Not final — shows processes where the selected event is not last
  • Flows through — shows processes containing the selected event
  • Does not flow through — shows processes that do not contain the selected event
Note

Event filters affect not only the widget display but also data in modal filter windows.

Number of Overtimes Filter

Select an event and process, then specify a minimum or maximum value—either manually or via slider.

Transition Duration Filter

Select a process and filter type:

  • Initial event — first event in the transition
  • Final event — last event in the transition
  • First occurrence — processes where the selected event appears first
  • Last occurrence — processes where the selected event appears last

You can also set a min/max duration and choose a unit (days, hours, minutes, or seconds).

Transition Existence Filter

Select a process and define:

  • Initial event — first event in the transition
  • Final event — last event in the transition

Then choose a transition type:

  • Exists — shows all existing transitions between the selected events
  • Does not exist — shows processes with no transitions between the selected events
  • Consecutive — shows processes where the selected events occur one after another
  • Not consecutive — shows processes where the selected events are not consecutive
Note

Consecutive and Not consecutive filters are unavailable if the selected events belong to different processes.

Widget Configuration in YAML

You can configure the widget not only in the visual editor but also in the YAML editor. The table below lists the keys and values available for configuration. For details on using the value key, refer to Dimension and measure values in YAML. Supported data formats are described on the corresponding page. General widget parameters are covered in Widget configuration in YAML.

Data Settings in YAML

KeyTypeDescription
titlestringTitle
showMarkdownbooleanDescription
markdownTextstringDescription text
markdownMeasuresMeasure in description
processesProcesses
eventMeasuresEvent indicator
transitionMeasuresTransition indicator
eventClickClick actions for events
transitionClickClick actions for transitions

Processes (key: processes)

To add processes, use the processes block with the following keys:

KeyTypeDescription
namestringProcess name
eventsstringShow events
colorstringColor:
- AUTO — auto
- BASE — solid

Event Indicator (key: eventMeasures)

To add an event indicator, use the eventMeasures block:

KeyTypeDescription
namestringEvent indicator name
valueEvent indicator formula
dbDataTypeenumEvent indicator data type
formatenumFormat
formattingenumFormatting
formattingTemplatestringCustom formatting
Only for CUSTOM formatting
showLabelsbooleanData labels
showSizebooleanLabels size
displayConditionDisplay (display condition)

Transition Indicator (key: transitionMeasures)

To add a transition indicator, use the transitionMeasures block:

KeyTypeDescription
namestringTransition indicator name
valueTransition indicator formula
dbDataTypeenumTransition indicator data type
formatenumFormat
formattingenumFormatting
formattingTemplatestringCustom formatting
Only for CUSTOM formatting
showLabelsbooleanData labels
showSizebooleanTransition thickness
sizeRangeTransition thickness range
displayConditionDisplay (display condition)
Transition Thickness Range (key: sizeRange)

To define the transition thickness range, include the sizeRange block inside transitionMeasures:

KeyTypeDescription
minnumberMinimum value
maxnumberMaximum value

Display Settings in YAML

KeyTypeDescription
paddingsstringSide paddings
titleSizenumberTitle size
titleColorTitle color:
- AUTO — auto
- BASE — solid
titleWeightenumFont weight:
- NORMAL — normal
- BOLD — bold
markdownTextSizenumberMarkdown description text size
Available only if Description is enabled
textSizenumberText size
indicatorsSizenumberIndicator size

Filtering Settings in YAML

KeyTypeDescription
filterModeenumFilter mode:
- DEFAULT — default
- DISABLED — disabled
ignoreFiltersbooleanIgnore filters
filtersFilters
eventFiltersEvent filters
stateNamestringState

Example of a Configured Widget in the YAML Editor

- key: PROCESSES_SPHERE
  apiVersion: "16"
  type: PROCESSES_SPHERE
  settings:
    displayCondition:
      mode: DISABLED
    textSize: 12
    ignoreFilters: false
    filters: []
    indicatorsSize: 12
    eventMeasures:
      - displayCondition:
          mode: DISABLED
        showSize: true
        dbDataType: INTEGER
        name: Number of events
        format: NUMBER
        value:
          mode: TEMPLATE
          templateName: eventsCount
          dbType: CH
        formatting: AUTO
        showLabels: true
      - displayCondition:
          mode: DISABLED
        showSize: false
        dbDataType: INTEGER
        name: Number of overtimes
        format: NUMBER
        value:
          mode: TEMPLATE
          templateName: overtimesCount
          dbType: CH
        formatting: AUTO
        showLabels: false
    transitionMeasures:
      - sizeRange:
          min: 1
          max: 8
        displayCondition:
          mode: DISABLED
        showSize: true
        dbDataType: INTEGER
        name: Number of transitions
        format: NUMBER
        value:
          mode: TEMPLATE
          templateName: transitionsCount
          dbType: CH
        formatting: AUTO
        showLabels: true
      - sizeRange:
          min: 1
          max: 8
        displayCondition:
          mode: DISABLED
        showSize: false
        dbDataType: INTEGER
        name: Median time
        format: DURATION
        value:
          mode: TEMPLATE
          templateName: medianTime
          dbType: CH
        formatting: AUTO
        showLabels: false
    sorting: []
    title: ""
    titleSize: 14
    stateName: State
    processes:
      - color:
          mode: AUTO
        name: Online credit application
        events:
          - Application submission
          - Client questionnaire preparation
          - Proposal agreement with client
          - Proposal selection with Client
          - Additional check 1
          - "Application submission: return to edit personal data"
          - Asset data entry
          - Bank rejection with explanation
          - Bank rejection
      - color:
          mode: AUTO
        name: Offline credit application
        events:
          - Application submission
          - Client questionnaire preparation
          - Proposal agreement with client
          - Proposal selection with Client
          - Additional check 1
          - "Application submission: return to edit personal data"
          - Asset data entry
          - Bank rejection with explanation
          - Bank rejection
    titleColor:
      mode: AUTO
    titleWeight: NORMAL
    showMarkdown: false
    markdownMeasures: []
    markdownText: ""
    eventClick: []
    transitionClick: []
    filterMode: DEFAULT
    eventFilters: []

Was the article helpful?

Yes
No
Previous
Process Explorer
We use cookies to improve our website for you.