Skip to content

Config database

The Config database is the central configuration database. It stores persistent application state that needs to survive restarts such as navigation structures, object registrations, scheduled jobs, saved user settings, and module-specific configuration across most MOD modules.

Alarms

Table Description
AlarmObjects Maps alarm names to their device keys. Used by scAlarmFinder to resolve which device an alarm belongs to.
mail_schedules Notification schedules for alarm emails and SMS. Each row defines a time window, active days, severity filter, alarm group filter, and the alarm state the schedule sends on. criteria holds a canonical key (all, active, acknowledged, unacknowledged or inactive) and defaults to active. slot2_active enables each weekday's second time window independently. Missing columns are added on start.
mailStats Log of every outgoing email and SMS attempt — timestamp, recipient, success flag, and any error message.
Table Description
navMenu The main navigation menu structure, stored as JSON. Built and updated by scNav at runtime.
subNavs Sub-navigation structures for individual views, stored as JSON. Managed by scSubNav.
viewPrivilegies Privilege requirements per Workview name. Controls which users can access a given view.

History

Table Description
History_SavedSignals_Project Project-wide saved signal groups in the History module. Available to all users.
History_SavedSignals_View View-specific saved signal groups in the History module. Scoped to a particular Workview.

Logbook

Table Description
logbook Logbook entries — text, topic, author, and timestamp. archived marks an entry as archived, hiding it from the list without deleting it. The column is added on start if missing, and the retired deleteMark column is dropped.
logbook_contexts Topic and context definitions used to categorise logbook entries.

Reports

Table Description
ReportQueue Pending report generation jobs waiting to be processed by scReports. Carries the report's display unit and factorArray, a comma-joined list of up to 15 per-signal scale multipliers.
reportSchedules Scheduled automatic report configurations — frequency, time window, logger, recipients, and output format. trigger_time, trigger_day and trigger_month set the exact send time. unit and factorArray store the same display unit and per-signal factors a manually created report uses.
reportStats History of completed and failed report jobs, including failure counts and timestamps. Also carries unit and factorArray.

Report columns are added automatically

unit and factorArray are added to all three report tables on first start, so an existing database migrates itself. A report created before the columns existed defaults to an empty unit and a factor of 1 per signal.

Documents

Table Description
documents Document metadata records.
document_files File references for documents — either a local file path or an online URL.
document_file_objects_mapping Maps document files to process objects by connection, device, system, and object name.

Objects

Table Description
ObjectList Maps process objects to the Workviews they appear in and their Data Store names. Used by scObjectFinder and scLinking to resolve object locations at runtime.

Control Curves

Table Description
StyrkurvaProfile Saved control curve profiles per tag. Stores the profile name, description, and a JSON representation of the curve.

Time Channels

Table Description
TimeChannelProfile Saved time channel profiles per tag. Stores the profile name, description, and a JSON representation of the schedule.