- 7 minutes to read

Custom Metadata

Transform Your Repository Into a Living CMDB

When integrations fail at 3 AM, you need instant answers: Who owns this? What's the SLA? Is this GDPR data? Without context in your tools, you hunt through SharePoint, email, and tribal knowledge while production burns.

Custom Metadata embeds business context directly in your operational systems. Attach metadata to every Integration, System, Service, Endpoint, Message Type, Resource, and more in the Nodinite Repository Model, and see it in log event details, monitors, and alerts. Your repository changes from a technical catalog into a living, governed CMDB that:

  • ✅ Enforces governance – Mandatory Fields stop integrations from going live without approval and ownership
  • ✅ Automates compliance – Tag GDPR/HIPAA/PCI integrations and produce audit lists in seconds
  • ✅ Enriches alerts – Alert Enrichment puts owner contact, SLA, and emergency procedures in the alert
  • ✅ Embeds context where you work – Metadata appears in log event details, monitors, alerts, and BPM diagrams
  • ✅ Enables portfolio intelligence – Portfolio Filtering filters repository lists, the Resources list, and Monitor Views on metadata values

The Custom Metadata field Technical Owner, its value Sarah Lind on INT1337 - Order-to-Cash, then a Log View search for ORD-10005, Show Details of the event, and the Repository Model tab showing the event's Integration with the same Technical Owner, animated walkthrough (7.12)
Animated walkthrough: one value from definition to operations. The field Technical Owner (a Text Field for Integrations) holds Sarah Lind on INT1337 - Order-to-Cash. In the Log View Contoso: Orders, search for order ORD-10005 and open Show Details of Order Received from Customer: the Repository Model tab shows the event's Integration with the same Technical Owner. The data comes from the Order-to-Cash demo.

Tip

Custom Metadata replaces the legacy Custom Fields feature. Use Custom Metadata for all new documentation; see Custom Metadata vs Custom Fields below.

How Custom Metadata Flows Through Your Operations

graph TB subgraph Define["Define Once"] A["fa:fa-tags Custom Metadata Fields
Owner, SLA, Compliance, Emergency Contact"] end subgraph Attach["Attach to Entities"] B1["fa:fa-puzzle-piece Integrations"] B2["fa:fa-cube Systems"] B3["fa:fa-gear Services"] B4["fa:fa-sign-in-alt Endpoints"] B5["fa:fa-lightbulb Resources"] B6["fa:fa-file Message Types"] end subgraph Enforce["Enforce Governance"] C1["fa:fa-lock Mandatory Fields
No save without Owner"] C2["fa:fa-shield-halved Validation
Prevent incomplete docs"] end subgraph Appear["Appears Everywhere"] D1["fa:fa-filter Repository Lists
Filters on metadata values"] D2["fa:fa-envelope Alert Emails
Owner + SLA + Runbook"] D3["fa:fa-bolt HTTP Webhooks
JSON with full metadata"] D4["fa:fa-file-lines Log Event Details
Repository Model tab"] D5["fa:fa-display Monitor Views
Enriched dashboards"] D6["fa:fa-diagram-project BPM Diagrams
Business context"] end subgraph Results["Business Results"] E1["fa:fa-stopwatch 95% faster incident response"] E2["fa:fa-check 100% ownership compliance"] E3["fa:fa-file-shield Automated audit reports"] E4["fa:fa-user-check Right person called first"] end A --> B1 & B2 & B3 & B4 & B5 & B6 B1 & B2 & B3 & B4 & B5 & B6 --> C1 & C2 C1 & C2 --> D1 & D2 & D3 & D4 & D5 & D6 D1 & D2 & D3 & D4 & D5 & D6 --> E1 & E2 & E3 & E4 classDef defineStyle fill:#2678BD,stroke:#2678BD,stroke-width:2px,color:#fff classDef attachStyle fill:#E47528,stroke:#E47528,stroke-width:2px,color:#fff classDef enforceStyle fill:#9E59BB,stroke:#9E59BB,stroke-width:2px,color:#fff classDef appearStyle fill:#93d16d,stroke:#3F827B,stroke-width:2px,color:#000 classDef resultStyle fill:#FFD525,stroke:#E47528,stroke-width:3px,color:#000 class A defineStyle class B1,B2,B3,B4,B5,B6 attachStyle class C1,C2 enforceStyle class D1,D2,D3,D4,D5,D6 appearStyle class E1,E2,E3,E4 resultStyle

Define metadata once (blue), attach it to any entity (orange), enforce mandatory fields (purple), see the context everywhere you work (green), and get measurable business results (yellow).

Real-World Impact

See how Custom Metadata solves critical operational challenges. Each scenario has its own page; the Scenario Index lists them all.

Scenario Business Value Results
Ownership Clarity at 3 AM Know instantly who owns each integration Alert shows Owner + Emergency Contact → 2 minutes to engagement (vs 45 minutes hunting)
Governance Enforcement Mandatory fields stop integrations from going live without approval 100% of Production integrations have documented Owner, SLA, and Approval
Compliance Automation Tag integrations by compliance requirement GDPR breach? Filter integrations → notify legal in 30 seconds (vs 2-day meeting)
Portfolio Intelligence Answer portfolio questions from live metadata "How many Gold SLA integrations does Finance own?" answered in 60 seconds (vs 2 days in Excel)

Complete Feature Reference

Feature What it gives you
Entity Coverage Define fields once and apply them to Integrations, Systems, Services, Endpoints, Message Types, Contracts, Articles, Resources, Domains, BPMs, Maps, and C4 Diagrams
Mandatory Fields Make a field mandatory per entity type so no one saves an entity in the Web Client without Owner, SLA, or Approval
Rich Data Types 13 user-entered data types for new fields: Text Field, Text Area, Markdown, Mermaid Diagram, Link, Item Link, Select, Check Box, Table, Attachment, Number, Image, and Shared File
Alert Enrichment Owner, SLA, Emergency Contact, and runbook links in email (XSLT) and HTTP Webhook (JSON) alerts
Portfolio Filtering Up to 4 filter rows on Repository overview pages, with Exists and Invert condition to find gaps

Rich Data Types for Complete Context

Beyond simple text fields: Select, Check Box (several values), Number, Links, Item Links, Tables, File Attachments, Image (from the Image Library), Mermaid Diagrams, and more, all entered by users. Older fields may use the legacy Multi Select, Date, or Date Time types; new fields can't be created with them. A Shared File value links to a file in the File Library; the SharedFilePolicy System Parameter controls which file types you can upload there and how Shared File links open. Competing products offer dropdowns; Nodinite offers a complete metadata ecosystem.

Operational Integration: Where It Actually Matters

Metadata isn't trapped in a documentation database; it's embedded where you work:

  • Repository lists – Filter Integrations, Systems, Services, and the other Repository lists, the Resources list, and the Monitor View live tab on metadata values (Portfolio Filtering)
  • Log Events – A log event's detail view has a Repository Model tab with the Custom Metadata of the event's Integration, Message Type, Endpoint, Services, and Contracts; the log rows in Log Views don't show metadata
  • Monitoring alerts – Alarm Plugins can include owner contact, SLA, and emergency procedures in the alert content
  • BPM diagrams – Metadata from linked Services is visible to business users
  • HTTP Webhook alerts – The JSON payload includes full Custom Metadata for automation (Jira, ServiceNow, Slack)
  • Email alerts – The default email templates list every Custom Metadata value of each Integration assigned to the alerting Monitor View, with no template change; Stylesheets (XSLT) choose or style the fields when you want branded HTML emails

A metadata-enriched alert turns "A resource changed state to Error" into "Call Henrik (+1-555-0123); if no response in 15 minutes, call Michael; runbook attached". Time to engagement drops from 45 minutes to 2 minutes. Alert Enrichment has the full before-and-after comparison, XSLT samples, and the webhook payload.

Custom Metadata vs Custom Fields

Both features add metadata to repository entities, but they serve different purposes. Custom Fields is the legacy feature for optional, global, informal notes (hidden by default through the DisableCustomFields System Parameter). Custom Metadata is the current feature for governance data: you scope each field to entity types, make it mandatory, filter on it, and see it in log event details, monitors, and alerts. The comparison table on the Custom Fields page lists every difference.

Get Started

Step Task Description
1 Define Custom Metadata Create metadata fields for your organization (Owner, SLA, Compliance Tags, and more)
2 Assign to entities Add metadata values to Integrations, Systems, Services, and Endpoints, or to a monitored Resource in Add or manage Resource
3 Enforce Mandatory Fields Mark critical fields as mandatory to prevent incomplete documentation
4 Configure alerting Show metadata in alert emails and webhooks so responders know who to call
5 Filter your portfolio Query your integration portfolio by metadata criteria

Common Questions

Next Steps