Developer Platform

Solibri API - Solibri Superrun Actions

Since: 26.9.0

All actions on this page are available in Solibri 26.9.0 and later.

Solibri Superrun has a list of specific actions you can perform. These correspond to actions you can also do manually in Solibri. Most actions have parameters you need to specify (for example, the parameter file specifies an input file path). Some parameters are optional, so you can leave them out if you don't need them.

In a .superrun file each action is a JSON object with a type, a params object, and an optional enabled flag:

{
  "type": "OPEN_MODEL",
  "params": {
    "file": "C:\\Users\\Models\\ifc\\MyModel.ifc",
    "discipline": "Architectural"
  },
  "enabled": true
}

The value of type is the action identifier listed for each action below. Actions are executed in the order they appear in the file. Disabled actions ("enabled": false) are skipped. See Solibri Superrun File Format for the surrounding file structure and for the value types used by parameters.

Actions

The actions you can perform with Solibri Superrun are:

The categories above are the same categories used by the action picker in the Superrun view.

Prerequisites

Most actions need something to already be available in the session, for example an open model or existing checking results. Each action below lists its prerequisites:

Prerequisite Meaning
Model At least one open model
Ruleset At least one open ruleset
Checking results Checking has been run
Presentation A presentation exists
Information Takeoff An Information Takeoff is open
Classification A classification is open

Prerequisites can be satisfied by an earlier action in the same workflow, or by the state of the session when the workflow starts. Validation warns about prerequisites that may be missing, but it does not prevent the workflow from running. See Validation.

Important
If you open an existing SMC model with Solibri Superrun, it may also include rules and rulesets, which are used in checking. Likewise, if a role is selected in Solibri, the resources related to it, such as classifications and rulesets, are loaded when Solibri starts and are used in checking in addition to the ones your workflow opens.

Here are the detailed descriptions of the actions:

Models

OPEN_MODEL

Example:

{
  "type": "OPEN_MODEL",
  "params": {
    "file": "C:\\Users\\Models\\ifc\\MyElModel.ifc",
    "discipline": "Electrical",
    "short_name": "ELE",
    "grid_visible": true,
    "categories": ["CATEGORY_NAME1", "CATEGORY_NAME2"]
  }
}

UPDATE_MODEL

Example:

{
  "type": "UPDATE_MODEL",
  "params": {
    "existing": "C:\\Users\\Models\\ifc\\Solibri Building.ifc",
    "with": "C:\\Users\\Models\\ifc\\Solibri Building - modified.ifc",
    "auto_update": true
  }
}

UPDATE_MODELS

Example: { "type": "UPDATE_MODELS", "params": {} }

SET_MODEL_SETTINGS

TRANSFORM_MODELS

SAVE_MODEL

Example: { "type": "SAVE_MODEL", "params": { "output_path": "C:\\Superrun\\models\\Building_saved.smc" } }

CLOSE_MODEL

Examples:

LIST_MODELS

Classifications

OPEN_CLASSIFICATION

CLOSE_CLASSIFICATION

LIST_CLASSIFICATIONS

Checking

OPEN_RULESET

OPEN_IDS_RULESET

UPDATE_RULE_PARAMETERS

CHECK

Example: { "type": "CHECK", "params": { "scope": "all" } }

AUTO_COMMENT

Example: Comment only critical issues that have not been accepted:

{
  "type": "AUTO_COMMENT",
  "params": {
    "zoom": true,
    "critical": true,
    "moderate": false,
    "low": false,
    "accepted": false,
    "rejected": true,
    "undefined": true
  }
}

WRITE_REPORT

RESULT_SUMMARY_REPORT

Example:

{
  "type": "RESULT_SUMMARY_REPORT",
  "params": {
    "output_path": "C:\\Superrun\\reports\\Building_result_summary.xlsx",
    "template_file": "C:\\Users\\Public\\Solibri\\SOLIBRI\\Report Templates\\Summary Report\\CheckingSummaryTemplate.xlsx",
    "title": "Checking Summary"
  }
}

SAVE_RULESET

CLOSE_RULESET

LIST_RULESETS

Presentations

CREATE_PRESENTATION

Example:

{
  "type": "CREATE_PRESENTATION",
  "params": {
    "name": "Coordination",
    "from_checking_results": true
  }
}

ADD_SLIDES

UPDATE_PRESENTATION

Important
If you need to retain issues that have been resolved from the checking results, do not run UPDATE_PRESENTATION immediately after rechecking. When updating from a BCF file, you can keep issues that are not present in the BCF by leaving remove_absent unset or false.

EXPORT_BCF

Example:

{
  "type": "EXPORT_BCF",
  "params": {
    "output_path": "C:\\Superrun\\reports\\Found issues.bcf",
    "version": "3.0",
    "scope": "all"
  }
}

GENERAL_REPORT

COORDINATION_REPORT

LIST_PRESENTATIONS

Information Takeoff

OPEN_ITO

CALCULATE_ITO

REPORT_ITO

Example:

{
  "type": "REPORT_ITO",
  "params": {
    "name": "Spaces",
    "output_path": "C:\\Superrun\\reports\\Spaces.xlsx",
    "template_file": "C:\\Users\\Public\\Solibri\\SOLIBRI\\Information Takeoff\\Templates\\Spaces.xlsx",
    "title": "Spaces"
  }
}

SAVE_ITO

CLOSE_ITO

LIST_ITOS

Visualizations

All visualization actions require an open model. The actions that operate on components take a filter_json parameter that selects the components to act on. The default filter matches all components. See Component filters for the filter syntax and for how to capture a filter from the current selection or from the Filter Table.

SET_AS_SELECTION

ADD_TO_SELECTION

REMOVE_FROM_SELECTION

HIDE_COMPONENTS

SET_VISIBLE

ISOLATE

MAKE_TRANSPARENT

MAKE_OTHERS_TRANSPARENT

COLOR_COMPONENTS

Example:

{
  "type": "COLOR_COMPONENTS",
  "params": {
    "filter_json": "[{ \"target\": \"ANY\", \"state\": \"INCLUDE\" }]",
    "color_hex": "#FF8800"
  }
}

RESET_COLORS_VISIBILITY

ZOOM_TO_COMPONENTS

MOVE_CAMERA

In the Superrun view, Capture Current View fills these values from the current 3D view.

SET_CAMERA_PROJECTION

GET_CAMERA_INFO

SET_SECTION_PLANES

In the Superrun view, Capture Current Planes fills this value from the current 3D view.

TAKE_SNAPSHOT

MEASURE_DISTANCE

In the Superrun view, From 2 Selected Components fills the GUIDs from the current selection.

System

CHANGE_LAYOUT

SHOW_HIDE_VIEW

RUN_SUPERRUN

EXIT

Pattern matching

Parameters that state they support wildcards accept:

Rule and ruleset name patterns (name in AUTO_COMMENT, rule_uuid in CREATE_PRESENTATION) use / to separate tree levels, and \/ for a literal slash inside a name.

Output verification

Actions that write a file—SAVE_MODEL, SAVE_ITO, SAVE_RULESET, WRITE_REPORT, GENERAL_REPORT, COORDINATION_REPORT, RESULT_SUMMARY_REPORT, REPORT_ITO, EXPORT_BCF, TAKE_SNAPSHOT, GET_CAMERA_INFO, and the LIST_* actions—verify after execution that the file at output_path exists. If the file is not created, the action fails and the run stops.