- 6 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 without Owner, SLA, and Approval
  • ✅ Optional on other types: required for Integrations, optional for Systems
  • ✅ Governance audits find the remaining gaps in seconds

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). 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. 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 saved before the field became mandatory ❌ Not changed. They keep their empty value until someone edits them; the next save in the Web Client then requires the field.
Items created or edited in the Web Client ✅ Checked. The form won't save until every mandatory field has a value.
Imports and other callers of the Web API ❌ Not checked. The API doesn't validate mandatory fields, so imports and API callers can still save items without them.

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).

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 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

User Action

  1. Navigate to Repository → Integrations
  2. Create a new Integration "Customer-Onboarding"
  3. Leave the Owner field blank
  4. Click Save

System Response

Nodinite marks Owner with a red asterisk and doesn't save the Integration. Fill in the field and save again.

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 saved through imports or the API, 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 and that Owner shows a red asterisk
  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