Custom Fields
Nodinite Custom Fields let you add, reuse, and manage flexible metadata for any repository entity. Use Custom Fields to document your systems integration landscape with supplementary information that support teams can reach when they need it.
- ✅ Enhance governance and compliance with structured documentation
- ✅ Improve support and maintenance with easily accessible metadata
- ✅ Automate and streamline operational processes with reusable fields
Tip
Custom Fields is a legacy feature and gets no new features. Use the newer and more structured Custom Metadata feature for new documentation, and move existing Custom Fields to it when you can.
The Web Client shows the Custom Fields menus only when the DisableCustomFields System Parameter is false. A new installation stores true, so the menus are hidden; an installation upgraded from a version before 7.0.15 has false and still shows them. The setting also hides or shows the Custom Fields cards on the edit and view pages and the Custom Fields in a Log Event's Repository Model tab.

Animated walkthrough: legacy, hidden by default. With DisableCustomFields true, Repository has no Custom Fields. Set it to false in System Parameters, save, and reload: Custom Fields is in the menu, and its list opens.
Custom Fields vs Custom Metadata: When to Use Each
Custom Fields and Custom Metadata both add metadata to repository entities, but they serve different purposes:
| Feature | Custom Fields | Custom Metadata |
|---|---|---|
| Status | ⚠️ Legacy, hidden by default | ✅ Current, recommended |
| Expected Usage | Optional supplementary information | Mandatory/expected governance data |
| Scope Control | Global across all entities | Scoped to specific entity types (Entity Coverage) |
| Mandatory Enforcement | ❌ No - always optional | ✅ Yes - required when saving in the Web Client (Mandatory Fields) |
| Filtering | ⚠️ Limited | ✅ Yes - 4 simultaneous filters New 6.1 (Portfolio Filtering) |
| Data Types | Text or File, each with a single value or multiple values | 13 user-entered types for new fields: Text Field, Text Area, Markdown, Mermaid Diagram, Link, Item Link, Select, Check Box, Table, Attachment, Number, Image, Shared File (Rich Data Types) |
| Operational Embedding | Display only | Shown in log event details (Repository Model tab), monitors, and alerts (Alert Enrichment) |
| Reporting | Manual export | Built-in filtering on Repository lists |
| Governance | Documentation only | Enforced policies |
| Use Cases | Notes, URLs, informal tags | Owner, SLA, Department, Compliance, Approval Status |
Use Custom Metadata for critical governance data (Owner, SLA, Compliance), and Custom Fields for supplementary informal notes.
What You Can Store in a Custom Field
Document your Repository Model with Custom Fields and deliver valuable information to key stakeholders when they need it most.
A Custom Field has one of two types, Text or File, and holds either a single value or multiple values:
- Single-value attribute from a list
- Multi-value attributes from a list
- Files (Word documents, images, zip files, ...)
A new Custom Field allows more than one value: Single Value is unticked until you tick it. The Custom Field Type and Single Value can only change while no item holds a value of the field. The values themselves are a list kept on the Custom Field (each with a value, a description, and a link; for File, the uploaded file), and each item picks from that list.

The Custom Fields Overview lists every defined Custom Field.
You can set, reuse, and assign Custom Fields to each entity in the Repository Model:
You see the information both in the Web Client and in email alerts sent from the Monitoring Service.
The lists are "global," but you can use different sets of values on the entities in the Repository Model.
Reuse Example
- Assign Henrik and Michael to Integration "INT001" with the Custom Field "Technical Contacts".
- Assign only Henrik to Integration "INT002" with the Custom Field "Technical Contacts".
- Assign Henrik, John, and Michael to Integration "INT003" with the Custom Field "Technical Contacts".
Tip
Share any information your organization needs by using Custom Fields. Custom Fields are key to successful support and maintenance services.
Single Value Example
Select only one value for the Custom Field when appropriate. For example, choose SLA Level—it makes sense to assign only one value for this type of field. For instance, select Gold from a list (Gold, Silver, Bronze).
Multi Value Attribute Example
Select more than one value for the Custom Field when needed. For example, assign multiple Technical Contacts—it makes sense to select more than one value for this type. For instance, select Michael and John from a list (Michael, Henrik, John, ...).
From File Example
Upload any file. The Web Client displays images directly.
Note
You see images rendered directly in the Nodinite Web Client for immediate reference.
Email alerts include links to files instead of attachments to conserve bandwidth, especially when you upload multiple or large files—this is by design.
Next Steps
- Add or manage Custom Field
- Add or manage Custom Metadata – The recommended alternative
- Add or manage Integration
- Add or manage System
- Add or manage Service
- Add or manage Endpoint
- Add or manage Message Types
Related Topics
- Custom Metadata – The current metadata feature
- Custom Fields Overview – Find and view Custom Fields in the Web Client
- Manage Custom Fields – Add, edit, delete, and restore Custom Fields
- Repository Model
- Integrations
- Systems
- Services
- Endpoints
- Message Types
- DisableCustomFields