System-Level Data

This chapter covers values and preferences settable at the system level — shared across all projects, listed under the System node in the Project Browser Tree.

System Values

System values are data automatically available to all projects simultaneously. You can override certain settings at the individual project level. Settable at system level:

• Release Levels ("Release Level")
• Design Abstractions ("Design Abstraction")
• Preferences ("System Preferences")
• Object Type Information (OTI) — both System and Project level OTIs can be created; Project level overrides System level when both exist
• Change Policies ("Change Policy")
• Option Maintenance, excluding option relationships ("Option Configuration")
• Rule libraries ("Rules and Constraints")
• SBOM Pattern Management
• Usage Definitions ("Usage Definition")
• Style Sets ("Styling Objects in Designs")

System values are created/maintained the same way as project-level settings (refer to the corresponding project-level topic for each value). Sub-topics: Importing and Exporting System Values, Copying System Values Between Projects.

System Preferences

In addition to Project Preferences (per-project), you can set values/preferences that automatically apply to all projects simultaneously — listed under the System node. See "System Preferences Dialog Box" for descriptions of all system preferences.

Caution: these preferences have system-wide impact and are intended for system administrators only. After saving a change, all client applications must be restarted for it to take effect.

Sub-topics: Default Web Services, Exporting System Preferences, Importing System Preferences.

Auto-Recovery of Data after a Crash

If an application crashes and is reopened, it runs an auto-recovery action on open designs, retrieving data saved into the \recovery directory under the client's TEMP directory. Saving happens in the background; a system preference (Error Reporting and Recovery) controls the save frequency.

Default frequency: save recovery data after 300 seconds of inactivity, and every 600 seconds otherwise.

Notes:

• Recovery files are keyed to the application that failed — only that same application can recover the designs. Available only in design applications where diagrams are edited.
• If the process is killed outright (e.g., via Task Manager), there is a short delay until Capital Manager detects the failure and offers recovery.

Managing Extensibility Plugins

The Plugins dialog box (Action > Plugins menu) lets you view and reload available extensibility plugins. It lists:

• Name — plugin name
• Version — plugin version
• Type — plugin type (e.g., Constraint or DRC)
• Language — Java or Script
• Path — absolute path to the parent folder (script plugin) or jar file (Java plugin)
• File — file name (script) or class name (Java)

The list is sortable by column. Selecting a plugin and clicking Details shows its description and implemented plugin interfaces in a separate dialog.

Audit Trail

Capital can maintain a record of all application-level events performed, including timestamp and initiating user — enabling traceability to identify actions that led to data loss/corruption. Logging is configured in System Preferences, by users with permission to both maintain system preferences and access the audit trail.

Sub-topics (landing page — titles listed, not individually expanded): Audit Trail Events, Viewing the Audit Trail, Filtering the Audit Trail, Clearing the Audit Trail Filter Criteria, Deleting Audit Trail Events, Preventing the Storage of User Information in Audit Trail Data.

Styling Objects in Designs

For designs in Capital HarnessXC, Capital Logic, Capital Integrator, and Capital Topology (including those generated by Capital AutoView Assist for Logic/Integrator), object styling in diagrams is controlled via a style set. Style sets are maintained at system level but applied to individual designs.

Each application has a Default style set. Creating additional style sets is a licensed operation — without the license, the create-new option is unavailable. See "Creating a Style Set" and the "Style Sets" section in the Diagram Styling User Guide for full details, including enabling/editing style sets and multi-user access considerations.

Sub-topics: Editing Style Sets, Exporting Style Sets (list continues per the doc's nav — not individually expanded here).

Query Expression

Various Capital functionality applies queries to data to identify objects for actions — e.g., conditional styling of design objects (tables, leader lines, text labels) based on query results against the represented data (example: styling insulation tables differently where insulation color is anything other than black).

Capital ships a default set of query expressions; more can be added. Query expressions are created at system level in Capital Project and are usable when styling diagrams in all projects. Custom Query Expressions can also be developed via the Capital extensibility architecture. Creating/editing queries is controlled by the Edit Queries user permission (see "Permissions" in the Capital User User Guide).

Rules and Constraints

Rules and constraints can be used in the design applications to control certain actions. See the Rules and Constraints topics in the Capital Design Tools – Common Functions User Guide for details.

Sub-topic: Rule Libraries.

Metrics

A metric is a single value calculated as a measure of "goodness" (e.g., cost or weight). Metrics are defined at system level and applied across all projects. See "Metrics" in the Capital Design Tools – Common Functions User Guide for concept details.

Metrics can be exported/imported from Capital Project. Sub-topics: Exporting Metrics, Importing Metrics.