- 4 minutes to read

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. Use the newer and more structured Custom Metadata feature whenever possible, and reserve Custom Fields for special cases.

The Web Client shows the Custom Fields menus only when the DisableCustomFields System Parameter is false. The default is true, so on a new installation the menus are hidden.

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 Single value, multi-value, files, plugin-loaded 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.

  • Single-value attribute from a list
  • Multi-value attributes from a list
  • Dynamically loaded (from plugin)
  • Files (Word documents, images, zip files, ...)

Custom Fields Overview list
The Custom Fields Overview lists every defined Custom Field.

Nodinite provides plugins for the most common scenarios. 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, ...).

Dynamically Loaded Example

When you open the Repository Model tab in the Web Client, Nodinite provides the Custom Field plugin with all available data from Monitoring or Logging. The plugin accesses web services or databases to return the value for the Custom Field at run-time. For example:

  • Display the temperature of the destination city for logged orders.
  • Generate a link to a documentation website (Wiki/SharePoint) based on provided data.

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