- 3 minutes to read

Custom Fields

Nodinite Custom Fields let you add, reuse, and manage flexible metadata for any repository artifact, empowering you to document your integration landscape with precision and clarity. This page explains how Custom Fields deliver value for system integration experts and organizations seeking robust governance and operational insight.

✅ Enhance governance and compliance with structured documentation
✅ Improve support and maintenance with easily accessible metadata
✅ Automate and streamline operational processes with reusable fields

Info

If possible, use the newer and more structured Custom Metadata feature. Custom Fields should only be used for special cases.

Use Custom Fields to document your Repository Model and provide valuable information to key stakeholders when it matters most for your system integration solutions.

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

Nodinite comes pre-loaded with plugins for the most common scenarios.
Custom Fields can be set, reused, and assigned to each artifact in the Repository Model.

Integrations
Systems
Services
Endpoints
Message Types

Information is displayed in both the Web Client and as part of email alerts sent from the Monitoring Service.

The lists are "global," but different sets of values can be used on the artifacts of the Repository Model.

Reuse Example

  • Integration "INT001" with Custom Field "Technical Contacts" can have Henrik and Michael assigned
  • Integration "INT002" with Custom Field "Technical Contacts" can have only Henrik assigned
  • Integration "INT003" with Custom Field "Technical Contacts" can have Henrik, John, and Michael assigned

Tip

Use Custom Fields to provide any information you may need to share with your organization. This is key to successful support and maintenance services.

Single Value Example

Use this when only one value can be selected for the Custom Field. For example, SLA Level—it is not logical to assign more than one value for this type of field.
Selected value example from a list (Gold, Silver, Bronze) could be Gold.

Multi Value Attribute Example

Use this when more than one value can be selected for the Custom Field. For example, Technical Contact—it is logical to assign more than one value for this type.
Selected value example from a list (Michael, Henrik, John) could be Michael and John.

Dynamically Loaded Example

When Nodinite renders the Repository Model tab in the Web Client, the Custom Field plugin is provided with all available data from Monitoring or Logging.
The plugin can access web services or databases to return the value for the Custom Field at run-time.

  • For example, logged orders can display the temperature of the destination city.
  • Another example: a generated link to a documentation website (Wiki/SharePoint) based on provided data.

From File Example

Any file can be uploaded. Images are displayed in the Web Client.
Images are rendered directly in the Nodinite Web Client for immediate reference. Since there can be multiple or large files, email alerts are sent with links to these files to conserve bandwidth—this is by design.

Next Step

Add or manage Custom Field
Add or manage Integration
Add or manage System
Add or manage Service
Add or manage Endpoint
Add or manage Message Types

Custom Fields Overview
Repository Model
Integrations
Systems
Services
Endpoints
Message Types