Feature Overview

Admin users define custom-field templates within the repository model. They then assign values for each applicable object, such as a Service or Message Type. Once filled in, these field values appear in overviews, search results and dashboards. So stakeholders can filter, group or report on things like business owner, region, version or criticality. The result: end users don’t just see generic tech metadata. They see meaningful business-context alongside integration artefacts.

Tailored Metadata Aligned to your Business

Custom Fields let you capture data that is specific and relevant to your organization’s unique integration needs, avoiding generic or insufficient documentation. This means business stakeholders and IT alike have access to repository entries that reflect real-world concerns, boosting relevance and adoption.

Enhanced Search, Filter and Grouping Capabilities

With custom field values captured consistently, you can build filtered views and reports. For example, show all Services in Region Nordic with Owner = “Finance”. This empowers end-users to quickly find relevant artefacts, speeding up tasks such as impact assessment or audit preparation.

Improved Reporting and Analytics

With enriched data attributes, businesses can perform more detailed analysis and generate insightful reports that align with operational goals, helping to identify trends and optimize processes. This clarity benefits users by reducing operational ambiguity when incidents occur, or changes are planned.

Enhanced Collaboration

Custom Fields let teams capture the exact metadata they need (like owners, SLAs, departments, or business context) directly where systems and integrations are documented, so everyone sees the same structured information in one place. This shared, consistent context reduces handover friction between teams, speeds up troubleshooting and impact analysis, and makes it easier for business, operations, and IT to collaborate around a single source.