- 4 minutes to read

Governance Enforcement

Stop architectural debt at the source. Nodinite Custom Metadata with Mandatory Fields makes sure no integration is saved without an owner, an SLA, and an approval.

  • ✅ Every Integration you save has a documented Owner, SLA, and Approval
  • ✅ Incidents resolved in 15 minutes instead of 4 hours of chaos
  • ✅ Zero ownership gaps in audit findings

The Challenge: Incomplete Integrations Going Live

Without Custom Metadata:

  • An integration is built without a documented owner
  • A Service is deployed to production without approval
  • A Resource is marked as critical but has no emergency runbook
  • 60% of integrations lack basic governance metadata

The result: architectural debt accumulates, followed by support chaos, knowledge loss, and compliance violations.

The Solution: Mandatory Metadata Fields

Custom Metadata enforces governance at creation time: integrations can't be saved without their mandatory fields.

Mandatory Field Rules

Each rule is one Mandatory checkbox per Repository Type:

  • An Integration can't be saved without: Owner, SLA Level, Approval Status
  • A Service can't be saved without: Owner, Change Window, Runbook
  • A Resource can't be saved without: Responsible Team, Emergency Contact
  • A Message Type can't be saved without: Business Ownership, Data Classification

The result: every entity saved from now on carries its governance context. Older entities that are still missing a value are one filter away, see Find the Remaining Gaps.

Real-World Impact

Metric Before After Value
Integration Completion 60% with documented owner 100% (mandatory field) Zero ownership gaps
Deployment Delays None (skip review, go live broken) 5 min (fill mandatory fields) Minimal friction, maximum governance
Audit Findings "30% undocumented integrations" "100% governance compliance" Zero regulatory findings
Support Knowledge Scattered, incomplete Centralized, mandatory Onboarding time cut 50%
Incident Time-to-Resolve Hours (hunting for context) Minutes (metadata in alert) SLAs protected

Implementation Workflow

Before Governance Enforcement

  1. A developer creates Integration "New-Payment-Processor"
  2. Deploys it to Production (no documentation required)
  3. The integration fails at 2 AM on Sunday
  4. Support tries to call the owner: "Who owns this?"
  5. Nobody knows
  6. Escalates to the manager: out of office
  7. Escalates to the architect: away on vacation
  8. 4 hours of chaos

After Governance Enforcement

  1. A developer creates Integration "New-Payment-Processor"
  2. Nodinite requires the mandatory fields before saving:
    • Owner: (required—must select from list)
    • SLA Level: (required—select Gold/Silver/Bronze)
    • Approval Status: (required—select Approved/Pending/Rejected)
    • Change Window: (required—fill in approved deployment windows)
  3. The developer fills in the metadata
  4. The integration is saved with complete governance
  5. The integration fails at 2 AM on Sunday
  6. Support reads the alert: "Owner: Sarah (555-0123), SLA: Gold, Approved by: VP Operations"
  7. Support calls Sarah immediately
  8. Issue resolved in 15 minutes

The difference: 4 hours of chaos vs 15 minutes of resolution, because the metadata was mandatory.

Common Mandatory Field Configurations

For Integrations

  • Owner (mandatory) - Who is responsible
  • SLA Level (mandatory) - Gold/Silver/Bronze
  • Approval Status (mandatory) - Approved/Pending/Rejected
  • Compliance Tags (mandatory, with a "None" value) - GDPR/HIPAA/PCI/None
  • Emergency Contact (optional) - Escalation point

For Services

  • Owner (mandatory) - Service owner
  • Change Window (mandatory) - When the service can restart
  • Runbook (optional) - Emergency procedures

For Resources (Monitoring)

  • Responsible Team (mandatory) - Responsible team or person
  • Emergency Contact (mandatory) - Escalation point
  • SLA Target (optional) - Uptime percentage

These configurations give you consistent governance across entity types. A field is mandatory or optional per Repository Type; it can't depend on another field's value, such as "required only for Gold SLA". Keep such fields optional and check them with a filter.

Find the Remaining Gaps

Use Portfolio Filtering to find entities that still lack a value, for example Integrations saved before Owner became mandatory, or Gold SLA integrations without an emergency contact:

Row 1: Owner, Exists + Invert condition
→ 12 integrations without an owner

Row 1: SLA Level = Gold
Row 2: Emergency Contact, Exists + Invert condition
→ 5 Gold SLA integrations without an emergency contact

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

How This Scenario Uses Nodinite Features

  1. Mandatory Fields – Required metadata per entity type
  2. Rich Data Types – Select fields for SLA Level and Approval Status
  3. Alert Enrichment – Owner and SLA in the 2 AM alert
  4. Portfolio Filtering – Find integrations with governance gaps

Next Steps