- 3 minutes to read

Make sure every integration has an owner

When something breaks, the first question is "who owns this?". Make the Owner field mandatory in Nodinite, and nobody can save an Integration in the Web Client without filling it in, so the answer is there when you need it.

  • ✅ Require an owner, an SLA level, or any other field on every Integration
  • ✅ Choose per entity type: required for Integrations, optional for Systems
  • ✅ Stop incomplete documentation at the moment it's written

When you need this

You own your team's integration documentation. Half the Integrations have no owner, and every incident starts with a hunt through email and old wiki pages. You want the gap to stop growing.

What you need

Do it

  1. In the Repository menu, open Custom Metadata.
  2. Click the Name of the field you want to require, for example Owner, to open it for editing.
  3. Under Repository Types, tick the entity type where the field belongs, for example Integrations.
  4. On the same row, tick Mandatory.
    Repository Types with a Mandatory checkbox per entity type (6.1.0.87)
    Each Repository Type has its own Mandatory checkbox, so a field can be required on Integrations and optional elsewhere.
  5. Repeat steps 3 and 4 for every other entity type where the field must be filled in, such as Services or Resources.
  6. Click Save.

What you'll see

  • The next time anyone creates or edits an Integration, the Owner field shows a red asterisk. The form won't save until the field has a value.
  • The field still shows on the other entity types you ticked without Mandatory, but there it stays optional.
  • Existing Integrations don't change until someone edits them.

Integrations saved before you ticked Mandatory may still have no owner, and so may Integrations added later by imports or other systems: imports and integrations through the API aren't blocked. To find them, filter the list on Owner with Check if any value exists and Invert condition ticked: see Find integrations by owner or SLA.

If it doesn't work

  • You can't change Repository Types: the form says that Data Type and Repository Types can only be changed while the field's Values list is empty. Ask your administrator before you clear values, because other people's documentation uses them.
  • You don't see Custom Metadata in the Repository menu, or can't save: you need the Modify permission on Custom Metadata. Ask your administrator.
  • You want a field to be required only in some cases, for example only for Production Integrations: that isn't possible. Mandatory is one checkbox per entity type. Keep the field optional and use the filter above to find the Integrations that still need a value.
  • An Integration has no owner even though the field is mandatory: it was saved before the rule, or added by an import or another system. Edit it and fill in the field, or use the filter above to find all of them.
  • Still stuck? See Support.

Next Steps