Asset Types
Asset Types provide structure to assets. Given the diverse nature of assets Panthora manages, defining Asset Types is crucial for specifying the kinds of assets to be stored and the fields they should possess.
For instance, food items and office electronics may require different fields and information.
Creating an Asset Type
Overview
Step 1
Specify the parent asset type for inheritance, as detailed in the Inheritance section.
Step 2
Name of the Asset Type.
Custom Fields
Custom Fields act as a form builder, dictating which fields will be available when creating assets.
Step 1
Add a new custom field.
Step 2
Specify the data type of this field, referencing the Data Types section.
Step 3
Field name. To include a name for assets, create a custom field titled "Name".
Step 4
Marking a field as required makes it mandatory for asset type creation.
Step 5
"Show in table" adds the field as a column in the asset table, aiding asset identification.
Step 6
The minimum length requirement varies by data type, ensuring at least 3 characters for strings.
Step 7
The maximum length limit, with no value allowing an infinite character count.
Step 8
Field order in asset creation can be adjusted via drag and drop.
Step 9
Fields can be removed, which also deletes data from assets containing these fields.
Data Types
| Data Type | Description |
|---|---|
| String | Single line input for any text, not suitable for numerical calculations. |
| Number | Accepts only numerical values, ensuring controlled input. |
| Boolean | Renders as a toggle switch, useful for binary states such as "Required". |
| Date | Includes a date picker for easy date selection. |
| Tag | Selection field for tags, facilitating asset categorization. Parent tag selection enables hierarchical tag usage. Further details in Tags documentation. |
Inheritance
Asset Types can inherit fields from a parent, streamlining the creation of related asset types without duplicating custom fields.
Example
The "Root" asset type includes a "Name" field, inherited by both "Electronics" and "Food". This inheritance ensures that creating an asset under "Food" automatically includes the "Name" field, even if not explicitly defined within the "Food" asset type.