Objects are organized by object type.
The object's type determines which fields, statuses, connections, forms, and workflows apply to an object. Object types become the core of your database’s custom configuration.
Object Type Hierarchy
When object types are designed, most object types will be defined “under” other object types in a hierarchy as shown in Figure 1-1. Whatever is true for a type is true for its sub-types. In technical term, the subtype inherits from the super type. For example, if the Special Project object type is under the Project object type, then everything that’s true for Projects will be true for Special Projects. If a Project can have a Project Update form, then a Special Project can have a Project Update form. If a Project can have a “managed by” connection, then a Special Project can also have a “managed by” connection.
In the example below, the File Server, Host Server, Desktop Computer, and Laptop Computer types are all under the Computer type, which in turn is under the Hardware type. Anything true (configured) for Hardware becomes true for computers, because a computer is a piece of hardware. And anything configured for a Computer becomes true for any File Server, because a File Server is a Computer and is a piece of Hardware. The phrase "is a" is important here. If the type hierarchy is designed correctly then every individual noun can be said that it "is a" for every type going up the hierarchy.
Like a zoo
One way to picture in your mind how the Object Type hierarchy works is to visualize the hierarchy of the animals in a zoo. What’s true for mammals is true for large cats, elephants, and bears. Whatever is true for large cats is also true for lions, and tigers. If mammals are air breathing and have live births then so do the large cats and the lions. This makes sense because a lion "is a large cat, which "is a" mammal.
If you say, “Give me a list of all the Lions”, it will include the zoo’s four lions. A list for all the large cats will include those four lions and all the tigers. A list of all the mammals will include the four lions, the tigers and all the other mammals.
The Object Type hierarchy works the same way. Referring again to image above, if you select Computer it will include all the computers including the file servers. Selecting Virtual Machine will include every virtual machine, including objects that belong to every sub-type. This method of selecting objects by their type works because a web server is a virtual machine in the same way that a lion is a mammal and is an animal.
The hierarchy concept is clean and simple (that's why we used the zoo example, a bear is seldom also a fish), but reality tends to be complex. A person could easily be a board member, customer, and founder all at the same time. A part can be a component and a finished product. A company can be both a customer and a vendor.
TejonBT handles reality by allowing any object to belong to multiple types, we call this Object Multi-Type. Every aspect of every type for the object is aggregated together and it all applies to the type. And, it's easy to add a new type tp an object once that new type applies in reality.