Working with object schemas

An object schema is your actual CMDB. It's a collection of object types and their attributes, objects and references between them. It also includes your configuration items, such as roles, icons, statuses, and automation rules. Object schemas work like maps that hold all of it together.  You can have many object schemas, and refer to objects inside them from your issues and requests.

Have one, or many

For example, you might have an HR object schema that captures all relevant HR data that adds value to your HR projects. It can contain information about employees, workplaces, and business areas, as well as information about employee assets, such as keyboards, monitors, and laptops. These can be linked together, so when you click on an employee, you immediately see other objects with information about their office, personally-assigned laptop, or even keyboard.

Here's what a sample schema from the ITSM template looks like:

  1. Object types: The list of all object types within a schema, organized in a tree structure.
  2. Objects: The list of objects within the selected object type, and details about them. As you can see, although all these objects are different, they use the same information, like Name, Model, or Serial Number.

Quick overview

Here's a video on object schemas if you'd like to get a quick overview:


Get started with object schemas

Here's a list of pages that have all the info you need:

Last modified on Feb 2, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.