Objects#
An object is the core unit of documentation in i-doit up. Every server, person, location, network, license, contract, organization, and so on is stored as an object that belongs to a class and is grouped into one or more collections.
Anatomy of an object#
An object has:
- a class that decides which categories it has and which attributes it can store;
- a unique name (visible everywhere) and a stable Object ID;
- a lifecycle stage: usually one of In operation, Active, Archived, or Deleted;
- a set of categories filled with attribute values; categories are reused across classes, for example General, Location, IP networking.
Day-to-day workflows#
- Browse and find objects in the Finder. Filter the list down with Set filter or save a search via Save search.
- Add an object with Create an object.
- Read and edit a single object on its details page.
- Apply changes to many objects at once with bulk actions.
- Group objects by location with Locations or by network with IP address management.
Lifecycle states#
Every object has a documentation state. Active objects are in regular use; Archived objects stay in the CMDB for historical purposes; Deleted objects are flagged for removal but still recoverable until they are permanently purged. You can change the state in bulk via the Edit dropdown or per-object on the details page.