Configuration identifiers framework
Summarize
Summary of Configuration Identifiers Framework
The Configuration Identifiers Framework in ServiceNow allows customers to customize the behaviors of Service Graph Workspace features across different workspaces. This framework is particularly beneficial when integrating features like the Service Graph Workspace Unified Map into other workspaces, enabling tailored settings for each use case.
Show less
Key Features
- Configuration Identifiers: Elements that contain custom settings for features applicable to specific workspaces. They override default behaviors for those workspaces.
- Default Config Identifier: Contains a single workspace-agnostic identifier with default settings. Only one identifier can be set to "Yes" to denote it as default.
- Role Requirements:
- sncmdbws.configeditor: Can modify child configuration tables.
- sncmdbws.configadmin: Can modify both config identifiers and child config tables.
- sncmdbadmin: Required to modify the default config records.
- Customizability: Customers can configure various aspects of the Unified Map, including node limits, de-duplication settings, and attribute display preferences.
Key Outcomes
By utilizing the Configuration Identifiers Framework, ServiceNow customers can effectively tailor their Service Graph Workspace experiences to meet specific operational needs, leading to improved functionality and user satisfaction in their integrated workspaces.
Configuration identifiers provide a framework that lets you customize some behaviors of a Service Graph Workspace feature, enabling different settings for that feature, on different workspaces. Most importantly, you can use this customization framework when integrating a Service Graph Workspace feature into another workspace.
Configuration identifier
A configuration identifier (also referred to as config identifier) is a configuration element within the configuration identifiers framework. A config identifier contains custom settings for a Service Graph Workspace feature, that is applicable to a specific workspace. A config identifier contains settings and table-driven configurations used in a UX application such as a workspace. Using config identifiers lets you for example, integrate Service Graph Workspace Unified Map into another workspace, with the integrated Unified Map being customized for the workspace. Config identifiers are stored in the Config identifiers [sn_cmdb_ws_config_identifier] table.
A config Identifier acts as the parent record for a set of configurations that are specific to a workspace and therefore overrides default behavior only for that workspace.
Default config identifier
Initially, the Config identifiers [sn_cmdb_ws_config_identifier] table in Service Graph Workspace, contains a single config identifier named ‘Default’ and which is workspace-agnostic. This Default config identifier has its Default column set to Yes, a setting that can't be modified. Only a single config identifier can be set to Yes, therefore, any additional config identifiers that you create are set to No.
The default config identifier contains default settings for Service Graph Workspace features. Any subsequent Config Identifier that you configure, is set for a specific workspace. When integrating a Service Graph Workspace feature into another workspace and there are no entries in the table-driven configuration for that feature, look-up uses the settings in the default configuration identifier.
Key roles
- sn_cmdb_ws.config_editor: Can modify child config tables, such as sn_cmdb_ws_config_property.
- sn_cmdb_ws.config_admin: Can modify both sn_cmdb_ws_config_identifier and child config tables.
- sn_cmdb_admin: Role required to modify default config records under the default identifier or the default identifier itself.
For more information about these roles, see Components installed with Service Graph Workspace.
Examples of Service Graph Workspace features using the configuration identifiers framework for feature settings
- Unified Map:
- Configure how many nodes can appear on a map
- Configure the default or maximum number of levels on maps
- Configure endpoint de-duplication on maps
- Configure which attributes to display in the Attributes panel
- Create a class profile of visible layers for classes
- Configure CIs to appear based on life cycle stage value
- Create CI: