Skip to content

System configuration

What it is for. It is the central access point to the platform settings.

When to use it. As a starting point to reach the configuration areas.

How to open it. From the Settings launcher.

What it shows and how to use it. Entries for Flow Engine, automations, routing, notifications, catalogues, users, system.

What happens next. The chosen area opens.

Notes. Shared configuration engine.

What it is for. It gives read-only access to the system configuration database.

When to use it. To query the system configuration in a controlled way.

How to open it. From the Settings launcher, System Configuration DB.

What it shows and how to use it. A read-only SQL query interface with the results; when you exit/close it you return to the Home.

What happens next. No changes to the data (read-only).

Notes. Read-only; navigation has been fixed to return to the root.

What it is for. It shows the platform version and build information.

When to use it. To check the version in production.

How to open it. From the Settings launcher, Platform Version.

What it shows and how to use it. Version, build and related information.

What happens next. No action (information only).

Notes. Useful for support.

What it is for. It configures Major Incidents: thresholds and classification.

When to use it. To set the activation rules for Major Incidents.

How to open it. From the Settings launcher / Major Incident Workbench (Major Incident configuration (MI Config)).

What it shows and how to use it. The thresholds (e.g. P1 over 30 min) and the P0–P3 classification.

What happens next. The automatic MI rules use these parameters.

Notes. See Major Incident Workbench – Major Incident configuration (Config MI).