- 8 minutes to read

Mandatory Metadata Fields

Stop Problems at the Source

When 60% of integrations have no documented owner, support turns into chaos at 3 AM when systems fail. Mandatory Custom Metadata fields stop new integrations from being saved without critical context, giving you instant escalation, predictable incident response, and a governance gap that stops growing.

  • ✅ Mark any Custom Metadata field as mandatory per Repository Type
  • ✅ No one saves an Integration in the Web Client, or edits one through the Web API, without Owner, SLA, and Approval
  • ✅ Optional on other types: required for Integrations, optional for Systems
  • ✅ Governance audits find the remaining gaps in seconds

Making the Custom Metadata field Technical Owner Mandatory for Integrations, animated walkthrough (7.12)
Animated walkthrough: in Administration → Custom Metadata, open the field Technical Owner, tick the lock next to Integrations under Repository Types, and Save and close. The closed lock means Mandatory; an open lock means optional.

Enforcement Flow

graph TD roCreate["fa:fa-plus Create or edit
an Integration
in the Web Client"] roValidate{"fa:fa-shield-halved Validation
Mandatory fields for
this Repository Type"} roOwner{"fa:fa-user Owner
Filled?"} roSLA{"fa:fa-star SLA Level
Filled?"} roApproval{"fa:fa-circle-check Approval Status
Filled?"} roError["fa:fa-circle-xmark Error
Cannot Save
Missing Required Fields"] roSuccess["fa:fa-check OK
Integration Saved"] roCreate --> roValidate roValidate --> roOwner roOwner -->|"Empty"| roError roOwner -->|"Filled"| roSLA roSLA -->|"Empty"| roError roSLA -->|"Filled"| roApproval roApproval -->|"Empty"| roError roApproval -->|"Filled"| roSuccess roError -.->|"Fill Fields"| roCreate style roCreate fill:#2678BD,stroke:#2678BD,stroke-width:2px,color:#fff style roValidate fill:#FFD525,stroke:#E47528,stroke-width:3px style roOwner fill:#9E59BB,stroke:#9E59BB,stroke-width:2px,color:#fff style roSLA fill:#9E59BB,stroke:#9E59BB,stroke-width:2px,color:#fff style roApproval fill:#9E59BB,stroke:#9E59BB,stroke-width:2px,color:#fff style roError fill:#c33d34,stroke:#c33d34,stroke-width:3px,color:#fff style roSuccess fill:#93d16d,stroke:#3F827B,stroke-width:3px

Mandatory field enforcement in the Web Client stops an Integration from being saved without its governance context. Blue = start, yellow = validation, purple = field checks, red = blocked (Error), green = saved (OK).

How Mandatory Fields Work

Define Required Fields Per Repository Type

When you add or manage Custom Metadata, select the Repository Types the field applies to and tick Mandatory for each type where it's required (see Entity Coverage). Each chosen type has a checkbox with a lock: an open lock is optional, a closed lock is Mandatory. Require all ticks every chosen type at once. For example:

Web Client enforcement: On the item page, a mandatory field shows a red asterisk, and the form won't save until the field is filled in. Save with the field empty is refused: the page scrolls up to Input error(s) Correct the input and then retry the save operation, with one line per missing field, named by its label (Technical Owner : Please fill out this field.), and the empty input is outlined in red. Nothing is stored. All item pages share the same editor, so this works the same way for every Repository Type.

What the Rule Doesn't Change

Situation What happens
Items created or edited in the Web Client ✅ Checked. The form won't save until every mandatory field has a value.
Items edited through the Web API New 7.12 ✅ Checked. An edit (PUT) of any of the twelve item types, or of their Custom Metadata, that leaves a mandatory field empty answers 400 with one error per field: The Custom Metadata 'Technical Owner' is mandatory and must have a value.
Items added through the Web API, created from logged events (Repository Binding), the C4 import, or MCP ❌ Not checked. These items have no Custom Metadata editor when they are created.
An Article, Resource or C4 Diagram edit that carries no Custom Metadata at all ❌ Not checked. The save keeps the stored values.
Items saved before the field became mandatory ❌ Not changed. They keep their empty value until someone edits them; their next save, in the Web Client or through the Web API, then requires the field.

Use the Governance Audit below to find the items that still lack a value.

One Rule Per Repository Type

Mandatory is a checkbox per Repository Type, and that's the whole rule: a field is either mandatory or optional for Integrations, for Services, and so on. Nodinite has no rule that makes a field mandatory based on another field's value, such as "required only when SLA Level is Gold". If a field matters only for some entities, keep it optional and use Portfolio Filtering to find the ones that still need it (see Governance Audit below).

Which Data Types Can Be Mandatory

The check applies to fields of the Data Types Text Field, Text Area, Link, Select, Check Box, Date, Number and Item Link. A Select or Check Box needs a picked value; the others need a non-blank value. A Check Box without values, and a Select whose values are all deleted, never block a save.

You can tick Mandatory on any field, but Table, Attachment, Markdown, Mermaid Diagram, Image and Shared File fields aren't enforced: neither the item page nor the Web API requires them.

Common Mandatory Field Configurations

For Integrations

Mandatory

  • Owner - Who is responsible for this integration (Henrik, Sarah, Ahmed)
  • SLA Level - Gold, Silver, Bronze (determines response time)
  • Approval Status - Approved, Pending, Rejected

Optional, Checked by Audit

  • Emergency Contact - Phone number for 24/7 escalation
  • Runbook URL - Link to emergency recovery procedure
  • Business Process Link - URL to business documentation

For Services

  • Technical Owner (mandatory) - Developer or DevOps contact
  • Technology Stack (mandatory) - .NET, Java, Python, BizTalk, MuleSoft, etc.
  • Change Window (optional) - When changes are allowed (e.g., "Saturday 2-6 AM EST")

For Resources (Monitored Components)

  • Responsible Team (mandatory) - Platform Team, Database Team, DevOps
  • Emergency Contact (optional) - On-call engineer phone number
  • Runbook URL (optional) - Emergency procedure document

For Message Types

  • Compliance Tags (mandatory) - GDPR, HIPAA, PCI DSS, SOX, or None
  • Data Classification (mandatory) - Public, Internal, Confidential, Restricted
  • Retention Policy (optional) - 7 years (financial), 90 days (diagnostic), etc.

Including a "None" value in a mandatory Select or Check Box field, such as Compliance Tags, forces an explicit decision without blocking entities that genuinely have no requirement.

Enforcement Scenario: Save an Integration Without an Owner

Adding an Integration with the mandatory Technical Owner left empty, the refused Save, then the field filled and saved, animated walkthrough (7.12)
Animated walkthrough: Add Integration with Technical Owner mandatory for Integrations. The first Save is refused; the second, with the field filled in, saves the Integration.

User Action

  1. Open Administration → Integrations and click Add Integration
  2. Name the Integration, for example INT1004: Contoso Customer Onboarding
  3. Leave Technical Owner empty: it already shows a red asterisk
  4. Click Save

System Response

Nodinite doesn't save the Integration. The page scrolls up to Input error(s) Correct the input and then retry the save operation with the line Technical Owner : Please fill out this field., and the empty field is outlined in red. Fill in Technical Owner (Sarah Lind) and click Save again: the Integration is saved, and its page shows the value under Custom Metadata.

Result: The Integration can't be saved in the Web Client without its governance context.

Governance Audit: Find Entities with Gaps

Entities saved before a field became mandatory, entities added through the API or created from logged events or the C4 import, and fields you keep optional can still lack a value. Use Portfolio Filtering on the overview page to list them:

  1. Open Repository → Integrations
  2. In Select Custom Metadata, pick the field, for example Owner
  3. Tick Check if any value exists and Invert condition: the row now matches integrations with no value
  4. Optional: click Add Filter to narrow the list, for example SLA Level = Gold
Integration Governance Audit

Owner, Exists + Invert condition:             12 integrations
Emergency Contact, Exists + Invert condition:  5 integrations
Runbook URL, Exists + Invert condition,
  and SLA Level = Gold:                        7 integrations

Assign the remediation to the integration owners, and run the same filters again to track progress.

Benefits of Mandatory Fields

Prevents Architectural Debt

Before Mandatory Fields

  • 60% of integrations have no owner
  • 40% have no documented SLA
  • Result: Support chaos, finger-pointing, blame culture

After Mandatory Fields

  • Every Integration saved in the Web Client since the rule was set has an Owner, SLA Level, and Approval Status
  • The audit filter shows exactly which older entities still need attention
  • Result: Predictable incident response, professional operations

Enforces Governance at Creation Time

No Integration is saved in the Web Client without a documented owner, an SLA, and an approval status. The result: fewer "shadow IT" integrations, and governance context that is there before the first incident.

Compliance Automation

GDPR Breach Investigation

  • Filter integrations: Compliance Tags = GDPR
  • Result: Instant list of affected integrations
  • Hand the list to the legal team in 30 seconds (vs a 2-day meeting to identify systems)

SOX Audit

  • Filter integrations: Department = Finance, then Add Filter: Approval Status = Approved with Invert condition
  • Result: Finance integrations that aren't approved
  • Remediate before the auditor arrives

The Compliance Automation scenario walks through the full GDPR case.

Configuration Guide

Step 1: Define Custom Metadata Fields

In the Web Client, open Repository → Custom Metadata and follow Add or manage Custom Metadata. Create these fields (see Rich Data Types for the types):

  • Owner (Select)
  • SLA Level (Select: Gold, Silver, Bronze)
  • Approval Status (Select: Approved, Pending, Rejected)
  • Emergency Contact (Text Field)
  • Runbook URL (Link)

Step 2: Mark Fields as Mandatory

For each field:

  1. Edit the Custom Metadata definition
  2. Under Repository Types, select the entity types: Integrations, Services, Resources, etc.
  3. Tick Mandatory for each entity type where the field is required
  4. Save

Step 3: Test Enforcement

Create a test integration:

  1. Open Add or manage Integration
  2. Leave the Owner field blank
  3. Click Save
  4. Verify that the Integration isn't saved: Input error(s) appears and the empty Owner is outlined in red
  5. Fill in the Owner field → Save succeeds

Step 4: Run a Governance Audit

Use the Exists + Invert condition filter from the Governance Audit section to find the entities that still lack a value, and assign the remediation to their owners.

Next Steps