Asset custom fields are not currently available in the user interface. Do not expect fields configured elsewhere in Settings to appear in Asset Registry, and do not use custom fields as part of a required Asset process yet.
OCTO Ops contains the underlying data structures for organization-scoped custom-field definitions, selectable options, and typed values. The current Settings field page lists available types, but creating and editing definitions is not implemented, and Asset records are not connected to the custom-field resolver.
Planned capability
When Asset custom fields are completed, they are intended to let an organization capture information beyond the standard Asset Registry fields while keeping values suitable for filtering and sorting.
The underlying type catalogue includes:
- Short text and Long text
- Number and Decimal
- Currency and Percentage
- Date and Date and time
- Duration
- Checkbox
- Single select and Multi select
- Person
- Department
- Project team
- URL, Email, and Phone
- Formula
Definitions are designed to be organization-specific and may be scoped by module, submodule, and record context. Select fields are designed to use managed options, and values are stored by type rather than as one unstructured block.
What users should do now
- Use the standard identity, acquisition, financial, responsibility, technology, remarks, category, location, status, condition, and attachment fields in Asset Registry.
- Agree on consistent use of those fields before importing or registering many assets.
- Use remarks or an approved attachment only for supplementary information that does not need structured filtering.
- Do not create a business process that assumes an Asset custom field can be required, searched, filtered, sorted, imported, or reported.
- Return to this page after the feature is released; it will be replaced with setup and usage procedures as part of that feature change.
Release requirements
Before this page is marked available, OCTO Ops must provide user-facing definition management, Asset Registry value entry and display, validation, access rules, filtering/report behavior, and tests. The help guide must then document each working behavior and any permission restrictions.