Skip to main content
Version: 3.1

Data Sources

Data Sources are the database connections Cortex uses to access your archived system data. Starting with v3.0, connections are managed directly inside the Cortex web app, allowing you to define any number of connections - including multiple connections to the same system type - without modifying server configuration files.

For background on how Data Sources relate to the installer and appsettings.json connection strings, see: Database Connections

Managing Existing Connections​

Where you edit a connection depends on how it was originally configured.

If a connection string was set up through the Cortex Installer or the Cortex System Manager, any changes to it must also be made through the Cortex System Manager. Because those connections are written to appsettings.json and loaded on startup, edits made to them in the web UI will be overwritten the next time the application restarts.

If a Data Source was created directly in the web UI (rather than via the installer or System Manager), you can continue to manage it entirely from the web UI without any risk of changes being reverted.

Source-system-specific settings​

Some source systems have extra configuration, found under their own tab when editing a data source (Data Sources > Edit Data Sources > edit the data source).

Cherwell​

  • Group Member Fields (Cherwell tab > Group Member Fields) - controls whether the search builder's field list for a related group business object includes every group member's fields, or only the group leader's. By default, only the group leader's fields are available when you add a search filter on a related group object. Checking Include all group member fields in search builder adds every field from every group member instead. This matters when the object you are searching has a relationship to a group leader - such as Specifics or a Configuration Item - and you need to filter or display a field that only exists on a group member, not the leader. With the setting enabled, searches and results grids correctly resolve fields from any group member.
  • Halo iframe embed (Cherwell tab > Embed / Halo) - the same Cherwell tab stores the iframe secret(s) used to verify embedded Halo custom tabs. See Halo integration for the full setup, including multiple-secret support added in version 3.1.2.

ServiceNow, Ivanti Neurons, Jira, ManageEngine​

Source-system-specific settings for these connections aren't documented here yet. If you're configuring one of these and something isn't covered, contact support.

note

Full documentation for this page, including screenshots, is coming soon.

See also​