- 1 minutes to read
FAQ - Mandatory Metadata Fields
Q: Can I require certain metadata fields to be filled?
A: Yes. Define mandatory fields per entity type (Integration, Service, Resource, Message Type).
Q: What fields should be mandatory?
A: Common mandatory fields:
- Owner - Always mandatory (who is responsible)
- SLA Level - Mandatory for production entities
- Approval Status - Mandatory before deployment
- Environment - Required to classify as Dev/Test/Prod
Integrations cannot publish without these.
Q: Can mandatory fields be conditional?
A: Yes. Set conditional mandatory rules:
IF Environment = Production
THEN Owner IS REQUIRED
THEN Approval Status IS REQUIRED
IF SLA = Gold
THEN Emergency Contact IS REQUIRED
THEN Runbook IS REQUIRED
IF Compliance Tags = GDPR
THEN Data Classification IS REQUIRED
Q: What happens if I leave mandatory fields blank?
A: Integration cannot publish. System displays: "Cannot deploy: Missing mandatory fields: Owner, Approval Status"
Q: Can I change mandatory fields over time?
A: Yes. Add new mandatory fields:
- New field becomes mandatory for future integrations
- Existing integrations grandfathered (but marked as "non-compliant")
- Run governance audit to identify gaps