Data are stored as objects in an EKM repository
and objects are defined by their type. Object
types are hierarchical, which means that they inherit their properties, actions, displays,
and type attributes from their parent (base type) and can add additional
properties, actions, displays, and type attributes of their own. EKM Object is the top-level base type for all EKM objects
and is described in the next section.
Object types include built-in
types that are supported by EKM, and custom types—including new
types and extended file formats—that are configured for your
workspace. Whenever an object is uploaded to EKM, it is automatically
assigned an object type based on its file extension, and in certain
cases, some additional logic. If EKM recognizes the object you
are uploading as a built-in or predefined custom type, then it will
assign the default type. For example, when you upload a file with
extension .cas, EKM will recognize it as
a Fluent Case type. Unrecognized
files are assigned the File type.
If there are multiple files that share the same extension and EKM cannot
resolve the object type correctly, it will use the preferred extension
you have specified in your global file extension preferences as the default.
Objects are displayed in the EKM interface as a tree of objects for easy navigation. The set of actions that you will be able to invoke on an object depends on its type, the permissions that are set for it, and whether access is restricted.