Skip to main content
Version: 2.4

Configuration Explorer

The Configuration Explorer is the primary way to understand how configuration is organized in tSM.

It presents configuration as a catalog of configuration items grouped by ConfigType, enriched with package and installation metadata, and connected to the editor of the selected item.

The Explorer is not just a screen. It represents the overall concept of how tSM configuration is:

  • grouped into business-oriented domains
  • discovered across many entity types
  • deployed using packages
  • tracked after installation

This page introduces the overall concept. Detailed behavior is described in dedicated pages:

Core idea​

tSM configuration is created in many different entity types, for example:

  • forms
  • processes
  • scripts
  • registers
  • listings
  • notifications

To make this manageable, each configuration item belongs to a ConfigType. ConfigType provides the business taxonomy that answers:

  • what area this configuration belongs to
  • which team owns it
  • which other items belong to the same area
  • which package scope should include it

This makes ConfigType the common grouping key for navigation, packaging, auditing, and administration.

Grouping model​

The conceptual grouping model is:

ConfigType
  -> EntityType
    -> Configuration Item

Example:

SDWAN
  Ordering
    Forms
      SiteSetupWizard
      OrderHeader
    Processes
      SDWANProvision

This structure separates two concerns:

  • ConfigType groups by business domain or capability
  • EntityType groups by technical configuration kind

As a result, administrators can browse one domain and still see all configuration types that belong to it.

For detailed ConfigType rules and attributes, see ConfigType.

Deployment model​

Configuration is typically moved between environments using packages. ConfigType is used to define the scope of a package — which items belong to it — so it serves as both a navigation aid and a practical deployment boundary.

After a package is installed, an Installed Package record tracks exactly what was deployed and whether the environment has drifted.

For the full packaging and deployment story, see Configuration Lifecycle.

Operational tracking​

After a package is installed, tSM can track:

  • which package last installed a configuration item
  • whether the item still matches the installed state
  • whether the item was modified after installation
  • which ConfigType subtree contains changed or missing package-managed items

This allows administrators to work not only with the current configuration, but also with its deployment history and drift status.

Installed Package tracking gives the environment-side operational view. ConfigType gives the grouping and navigation view. The Configuration Explorer combines both.

User interface model​

The Explorer uses a strict two-pane layout:

LEFT  = Smart configuration tree
RIGHT = Context editor

The left side provides structured navigation through:

  • ConfigType nodes
  • EntityType nodes
  • configuration item nodes

The right side displays the context of the selected node:

  • ConfigType summary
  • EntityType contents
  • configuration item editor

This makes navigation fast and keeps the mental model simple.

Screen layout​

Configuration Explorer
==============================================================================
Configuration Tree                     | Configuration Editor
---------------------------------------|--------------------------------------
★ Favorites                            | Form: SiteSetupWizard
                                       |
▾ SDWAN                                | ConfigType: SDWAN.Ordering
  ▾ Ordering                           | Package: SDWAN
    ▾ Forms                            | Installed Version: 1.4.0
      SiteSetupWizard  ⚠  SDWAN        | Drift: Changed
      OrderHeader      ✓  BSS          |
                                       | [ Configuration editor ]
    ▾ Processes                        |
      SDWANProvision  ✓  SDWAN         | [Save] [Compare] [History]
                                       |
▾ BSS                                  |
  ▾ ProductCatalog                     |

The left pane displays a smart configuration tree.

Nodes may represent:

Node typeDescription
ConfigTypeCapability or configuration domain
EntityTypeConfiguration type, for example Form, Process, Script
ItemIndividual configuration object

Users typically navigate in this order:

  1. Expand ConfigType
  2. See available entity types and counts
  3. Expand one entity type
  4. Select a concrete configuration item

This gives users one catalog that spans many configuration technologies without flattening everything into one list.

Item metadata in the tree​

Configuration item nodes can display key metadata directly in the tree, for example:

SiteSetupWizard ⚠ SDWAN
OrderHeader ✓ BSS
ValidateOrder ✓ Infra

Typical metadata shown next to the item:

  • drift indicator
  • latest package
  • package version in tooltip
  • owner team in tooltip
  • last modified information in tooltip

This lets users understand the state of the item before opening the editor.

For the source of package and drift information, see Installed Package.

Favorites​

Favorites allow users to bookmark frequently used nodes.

Favorites can reference:

  • ConfigType nodes
  • EntityType groups
  • configuration items

They appear at the top of the tree and behave exactly like normal navigation targets.

This is especially useful in environments where administrators repeatedly work in the same few domains and forms.

Typical usage​

Browse configuration by solution area​

Explorer
-> SDWAN
-> Ordering
-> Forms
-> SiteSetupWizard

Investigate package drift​

Explorer
-> navigate to ConfigType subtree
-> look for warning indicators
-> open item
-> compare current and installed state

Review package-managed configuration after deployment​

Open ConfigType subtree
-> filter items installed by package
-> inspect changed or missing items

Configuration beyond tSM​

The Configuration Explorer is the primary in-app interface for browsing and editing configuration. The full configuration lifecycle — versioning, packaging, transferring, and deploying configuration across environments — is handled by external tooling (tSM Studio, tSM CLI, CI/CD pipelines).

For details on the full lifecycle, tools, and workflow examples, see Configuration Lifecycle.

Best practices​

Use ConfigType consistently​

Every configuration item should belong to the correct ConfigType. This is the basis for navigation, packaging, and reporting.

Keep package scope aligned with ConfigType​

Whenever possible, package scope should follow business or capability boundaries already expressed by ConfigType.

Use the Explorer for discovery​

The Explorer is the recommended way to understand how configuration is distributed across domains, entity types, and packages.

Use detailed pages for exact behavior​

This page explains the concept. Detailed rules and lifecycle behavior are documented in ConfigType, Installed Package, Change Sets, and Configuration Lifecycle.

Summary​

The Configuration Explorer brings together three important concepts:

  • ConfigType for grouping and navigation
  • packages for deployment between environments
  • installed package tracking for operational visibility and drift evaluation

It gives administrators a single, structured way to browse, understand, and edit configuration across the system while preserving the underlying ownership of each configuration entity.

See also​