- 8 minutes to read

Where Custom Metadata Applies

Universal Application Across Every Entity

Custom Metadata isn't limited to documentation: it attaches to the entities across your Nodinite environment. Define metadata fields once ("Owner," "SLA," "Compliance Tags"), scope each field to the entity types where it makes sense, and apply it across your integration landscape. This page describes the entity coverage of Custom Metadata, entity type by entity type.

  • ✅ One field definition reused on every entity type you select
  • ✅ Each field optional or mandatory per entity type
  • ✅ The same context in log event details, alerts, list filters, and BPM diagrams

Adding Resources and Message Types to the Repository Types of the Text Field Support Team, then setting its value on a Resource, animated walkthrough (7.12)
Animated walkthrough: the field Support Team applies to Integrations only. Add Resources and Message Types under Repository Types and Save and close: the Resource INT001: Receive Order from Service Bus Queue now lists Support Team in its Custom Metadata panel, set to Integration Support.

Explore by category: Repository Entities | Monitoring Resources | Business Process Management | Operational Views | Documentation and Knowledge

Universal Metadata Flow

graph LR roDefine["fa:fa-wrench Define
Custom Metadata
Owner, SLA, Tags"] roRepo["fa:fa-sitemap Repository
Integrations
Systems
Services"] roMonitor["fa:fa-bell Monitoring
Resources"] roBPM["fa:fa-diagram-project BPM
Process Models
Domains"] roLogs["fa:fa-file-lines Log Event Details
Repository Model tab"] roAlerts["fa:fa-envelope Alerts
Email + Webhook
Enriched Context"] roLandscape["fa:fa-diagram-project BPM View Page
Process Owner
Compliance Scope"] roReports["fa:fa-filter List Filters
Repository, Resources,
Monitor View live tab"] roDefine ==>|"Apply Once"| roRepo roDefine ==>|"Apply Once"| roMonitor roDefine ==>|"Apply Once"| roBPM roRepo -->|"Shown in"| roLogs roMonitor -->|"Shown in"| roAlerts roBPM -->|"Shown on"| roLandscape roRepo -->|"Filtered in"| roReports style roDefine fill:#2678BD,stroke:#2678BD,stroke-width:3px,color:#fff style roRepo fill:#93d16d,stroke:#3F827B,stroke-width:2px style roMonitor fill:#93d16d,stroke:#3F827B,stroke-width:2px style roBPM fill:#93d16d,stroke:#3F827B,stroke-width:2px style roLogs fill:#FFD525,stroke:#E47528,stroke-width:2px style roAlerts fill:#FFD525,stroke:#E47528,stroke-width:2px style roLandscape fill:#FFD525,stroke:#E47528,stroke-width:2px style roReports fill:#FFD525,stroke:#E47528,stroke-width:2px

Define Custom Metadata once (blue), apply it to entities (green), and see each entity's own values where you work (yellow). Universal application keeps your entire integration landscape consistent.

Repository Entities

You choose the entity types for each field under Repository Types when you add or manage Custom Metadata, and you can mark the field as mandatory per type. The picker offers twelve types: Integrations, Systems, Services, Contracts, Endpoints and Message Types (this section), Resources, BPMs and Domains, and Articles, Maps and C4 Diagrams.

The Data Type can only be changed while the field's Values list is empty. Repository Types can be added at any time, also after the first save of a Select or Check Box New 7.12. A Repository Type can be removed only while no item of that type has a value: its chip is locked, its tooltip says how many items have values, and a line under the picker lists those types.

Integrations

What: Business-facing integration flows (e.g., "Order-to-Cash," "Patient Admissions")

Typical metadata:

  • Owner (Henrik, Sarah, Ahmed)
  • Department (Finance, HR, Healthcare)
  • SLA Level (Gold, Silver, Bronze)
  • Compliance Tags (GDPR, HIPAA, PCI DSS)
  • Approval Status (Approved, Pending, Rejected)
  • Business Process Link (URL to documentation)

Why it matters: When an integration fails, the alert includes Owner + Emergency Contact, when the Integration is assigned to the Monitor View that alerts → 2-minute engagement vs 45-minute hunting.

Learn more: Add or manage Integration | Integrations Overview | Alert Enrichment

Systems

What: Connected applications (SAP, Salesforce, Payment Gateway, Warehouse Management)

Typical metadata:

  • System Owner (IT contact responsible for system)
  • Vendor (SAP, Oracle, Microsoft)
  • Environment (Production, Test, Dev)
  • Criticality (Mission Critical, Standard, Low Priority)
  • Maintenance Window (Saturday 2-6 AM EST)

Why it matters: Know instantly if a system failure affects production or test. A System's Custom Metadata isn't in alerts: to name the owner in an alert, put the owner on the Resource that monitors the system.

Learn more: Add or manage System | Systems Overview

Services

What: Technical integration services and orchestrations (API endpoints, message processors, data transformers)

Typical metadata:

  • Technical Owner (Developer/DevOps contact)
  • Technology Stack (.NET, Java, Python, BizTalk)
  • Deployment Date (2024-03-15)
  • Change Window (Requires approval for changes)
  • SLA (4-hour response for Gold services)

Why it matters: Technical context embedded in operational systems. DevOps knows who built what and when.

Learn more: Services Overview

Contracts

What: Contracts – one end of a communication chain, belonging to a System and linking its Message Types and Endpoints

Typical metadata:

  • Contract Owner (business or technical contact)
  • Agreement Reference (link to the partner agreement)
  • Compliance Requirement (GDPR, PCI DSS)

Why it matters: The business agreement behind each message exchange is documented where operations can see it.

Endpoints

What: Connection points (URLs, file paths, message queues, database connections)

Typical metadata:

  • Endpoint Type (REST API, SOAP, SFTP, Database, Queue)
  • Security Level (Public, Internal, Confidential)
  • Authentication Method (OAuth, API Key, Certificate, Kerberos)
  • Rate Limit (1000 requests/hour)
  • Firewall Rules (Requires port 443 open)

Why it matters: Security audits in seconds. Filter Security Level = Public, then add a row for Authentication Method with Exists + Invert condition → every Public endpoint with no documented authentication.

Learn more: Endpoints Overview

Message Types

What: Transaction types flowing through integrations (Invoice, Purchase Order, Patient Record, Payment)

Typical metadata:

  • Business Document Type (Financial, Healthcare, Logistics)
  • Compliance Requirement (GDPR personal data, HIPAA protected health info)
  • Retention Policy (7 years for financial, 90 days for diagnostic)
  • Encryption Required (Yes/No)
  • PII Data (Contains personally identifiable information)

Why it matters: GDPR breach? Filter "Show all Message Types with GDPR tag" → notify legal in 30 seconds.

Learn more: Message Types Overview

Monitoring Resources

Resources (Monitored Components)

What: Any monitored Resource (CPU, Memory, Disk, Database, Web Service, Integration Atom, Cloud Function)

Typical metadata:

  • Responsible Team (Platform Team, Database Team, DevOps)
  • Escalation Contact (On-call engineer)
  • SLA (99.9% uptime for Gold resources)
  • Criticality (Critical, Standard, Low)
  • Emergency Procedure (Link to runbook PDF)

Why it matters: CPU hits 95% → the alert includes "Call Michael (Platform Team) at +1-555-0123, Emergency Runbook: [link]".

Business Process Management

BPM (Business Process Models)

What: Visual process flows showing integration steps (Order-to-Cash, Procure-to-Pay, Hire-to-Retire)

Typical metadata:

  • Process Owner (VP Operations, CFO)
  • Annual Volume (500,000 orders/year)
  • Revenue Impact ($50M annually)
  • Compliance Scope (SOX, GDPR, ISO 27001)
  • Last Audit Date (2024-Q2)

Why it matters: Business users see the process owner, revenue impact, and compliance scope on the BPM's View page, next to the process flow.

Learn more: BPM

Domains (Organizational Swimlanes)

What: Business units or functional areas (Finance, HR, Supply Chain, Customer Service)

Typical metadata:

  • Domain Owner (Department head)
  • Budget Code (for chargeback reporting)
  • Governance Policy (Link to governance document)
  • Audit Frequency (Quarterly, Annual)

Why it matters: The domain owner, budget code, and governance policy are documented once for every BPM in the domain.

Learn more: Domains

Note

BPM requires a BPM license, and Domains are available with either the BPM license or the Mapify license. See License Options and Feature Matrix.

Operational Views

Log Views and Monitor Views aren't Repository Types, so you don't attach Custom Metadata to the views themselves. They are where people work with the entities that carry it:

  • Log Views: saved, role-scoped filters over log events. Give each audience its own view, such as "Finance Errors" for the Finance team. The log rows show no Custom Metadata, and you can't filter a log search on it; open a log event and its Repository Model tab shows the Custom Metadata of the event's Message Type, Endpoint, Services, and Contracts.
  • Monitor Views: group monitored Resources. Which people receive an alert is set by the Alarm Plugins on the Monitor View, never by Custom Metadata values. The alert content lists the changed Resources' own Custom Metadata and that of the Integrations assigned to the Monitor View, see Alert Enrichment.

Documentation and Knowledge

Articles

What: Documentation pages, runbooks, troubleshooting guides, architecture diagrams in Articles

Typical metadata:

  • Document Type (Architecture, Runbook, FAQ, Best Practice)
  • Owner (Technical writer, Architect)
  • Last Reviewed (2024-10-15)
  • Review Frequency (Quarterly)
  • Approval Status (Approved, Draft, Archived)

Why it matters: Keep documentation current. Readers see when an article was last reviewed and who owns it. Filter the Articles Overview on these fields with the Custom Metadata filter, for example to list every Runbook that is still a Draft (see Portfolio Filtering).

Maps and C4 Diagrams

What: Maps in Mapify and diagrams in C4 Diagrams

Typical metadata:

  • Diagram Owner (Architect)
  • Scope (Finance landscape, Order-to-Cash)
  • Approval Status (Approved, Draft)

Why it matters: Readers know who maintains a picture of the landscape and whether it's approved.

Key Benefits of Universal Coverage

Define Once, Use Everywhere

Create the "Owner" field once and apply it to Integrations, Services, Resources, BPMs, Domains, and more. The result is consistent governance across the entire landscape. Add more types later as the field proves useful; a type can be removed only while none of its items has a value (see Repository Entities).

Each Item Keeps Its Own Values

Every item stores its own Custom Metadata values. Nothing is copied or inherited along relationships: an Owner set on an Integration doesn't appear on its Services, Systems, or Endpoints. Give each item its own value, or point to a related item with an Item Link field (see Rich Data Types).

Where related metadata does come together:

  • Log Events → a log event's detail view has a Repository Model tab with the Custom Metadata of the event's Message Type, Endpoint, Services, and Contracts
  • Monitor alerts → Owner + SLA + Emergency Contact in the alert content, from the changed Resources and from the Integrations assigned to the Monitor View (see Alert Enrichment)
  • BPMs → the BPM's own metadata on its View page, next to the process flow

Filter Lists by Metadata

Portfolio Filtering works on the Repository lists, the Resources list, and the Monitor View live tab (not on log searches), and answers questions such as:

  • "Show all Gold SLA integrations without owners" → Governance gap report
  • "Show all GDPR integrations in Production" → Compliance audit
  • "Show all Services using deprecated technology" → Technical debt report

The result: executive visibility into integration landscape health.

Next Steps