Terms and abbreviations used in Data Content Management application and this Wiki.
| Term / Abbreviation | Definition |
|---|---|
| Actual record | Actual data record in a ServiceNow table. As compared to Desired record which is still just a planned record inside DCM and not really created into the matching table. |
| AI | Audit instance |
| AM | Audit message |
| AR | Audit result |
| Audit | See "DCM Audit". |
| Audit instance | Each audit "run" creates a single Audit instance record which groups together all Audit results and messages related to that audit. |
| Audit message | Audit messages will record how current data compares to all details defined by the Blueprint version. Audit messages include information about the Real record and deviation level together with audit result type to identify what data we are auditing and how well it matches with the blueprint. |
| Audit result | Audit result records are created for each actual record from the root class which is included into an audit instance. For example, if you have a Blueprint version where "Business Application" is the root class, then each Business Application record will create and "Audit result" record that relates Audited record to all audit messages created by an audit instance. |
| Available Class | Classes defined to available in Blueprint Designer. ServiceNow instances has lot of system tables and other data that will never be used on blueprints. Available classes define which classes can be used on blueprints. DCM Admin can change and create new available classes definitions. See Available Classes configuration |
| Blueprint | Visual representation of a data model including classes and their links to each other. DCM blueprints use a UML-like syntax to define how classes should be connected each other including multiplicity definitions for links. |
| Blueprint container | Represent a class used (ServiceNow tables) in the blueprint. |
| Blueprint container conditions | Blueprint containers can include conditions which are used to filter records that are valid for the container. For example only include "Active" records from the User table. |
| Blueprint container relationship | Links or relationships between Blueprint containers. Link can be either one-to-many Reference or many-to-many type of relationship. |
| Blueprint Designer | Blueprint Designer is a visual data modelling tool that information architects or system admins can use to create and maintain data model blueprints on ServiceNow. Read more about Blueprint Designer. |
| Blueprint element | Reusable part of a Blueprint that can be linked to Audit Messages. Blueprint Elements are either containers or links defined into one or more blueprint versions. For example when same Class is used on two different blueprint versions (or just twice in the same blueprint version), it's considered as single Blueprint element. |
| Blueprint library | See "Library" |
| Blueprint links | Links are connections between classes. Two types of links are available:
|
| Blueprint status | Blueprints have a lifecycle which is indicated by a status value. Each blueprint can have up to one published version and multiple other versions in different states of the lifecycle. Read more about Blueprint lifecycle. |
| Blueprint template | Blueprint templates are model blueprints that can be used to create new blueprints. Templates can not be used to plan data. Templates are available in the Blueprint library and when creating new blueprints. |
| Blueprint version | DCM application takes care of blueprint versioning and one blueprint can have multiple versions defined. Each blueprint can have only one Published version at a time. |
| BP | Blueprint |
| BPE | Blueprint element |
| BPV | Blueprint version |
| Class | Classes can be either existing tables in the ServiceNow instance or Desired classes, meaning planned, not existing tables in the blueprint. |
| Content set / Data content set | Data content set is a single set of records and links related to a blueprint stored in the DCM Safety Zone. This staging area is used when planning data using Data Content Planner. |
| Content Set Item | One record in a Data Content Set. The black circles on the canvas in Data Content Planner. Also known as Data Content Set Item. |
| CSI | Content Set Item |
| Data Content Planner | Graphical tool for data analysts to manage data content by making use of blueprints. The selected blueprint guides the user through the content creation process. Read more about /wiki/spaces/DCMW/pages/1563166529. |
| Data Population Wizard | An automated functionality to preview and validate data changes and update them to ServiceNow production tables safely. Read more about Data Population Wizard |
| DCM | Data Content Manager |
| DCM Audit | A functionality which compares the current data content against the blueprint's rules & conditions, and reports any deviations. Read more about Data Audit. |
| DCM Safety Zone | All blueprints and data content sets are planned in the isolated staging area called DCM Safety Zone, without of any risk of harm for business critical production data. |
| DCP | Data Content Planner |
| DCS | Data Content Set |
| Deprecated blueprint | Deprecated blueprints are older versions of a blueprint which also has a newer Published version or blueprints which are not encouraged to be used anymore. Deprecated blueprint can still be used to plan new data content sets and to audit existing data. |
| Desired Class | New Class which doesn't exists as a ServiceNow table yet in the system. Desired classes can be used on new Blueprints for planning, but blueprint can not be published before all Desired Classes are actually added in to the system. |
| Desired Links | New links which doesn't exists as a ServiceNow tables (m2m) or references yet in the system. Desired links can be used on new Blueprints for planning, but blueprint can not be published before all Desired Links are actually added in to the system. |
Desired Record | Desired records are new records added to data content sets using Data Content Planner. These records do not exist in the actual ServiceNow tables, but are recorded as part of planning into DCM Safety Zone. |
| DPW | Data Population Wizard |
| Field plan | Field plan is set of attributes and values to a Desired Record before it's populated into an actual ServiceNow table. Fields plan are required for new Desired Records and can be maintained in Data Content Planner. Starting at DCM R3, Field plans are also available for actual records, not only Desired records. |
| Field planner | Field planner is a popup window in Data Content Planner used to manage Field plans for Desired Records. |
| Field content | Field content is the actual field value for single attribute in a Field plan. |
| Library | Library is a place to store and manage your local blueprints, blueprint templates and data content sets. |
| Published blueprint | Ready and approved blueprint version which has been Published into Blueprint library for new Data Content creation and audits. Each Blueprint can have maximum of one Published blueprint version. Read more about Blueprint lifecycle |
| Record | Record is one instance of a class. One row in an actual ServiceNow table or a Desired record. |
| UAM | Unique audit message |
| Unique Audit Messages | Unique version of audit messages. When two audit messages have the same real record, blueprint element and audit result type, they are considered duplicates and related to single Unique audit message. Unique audit messages were introduced in DCM R4.0. |