Skip to main content

How to Integrate with the Business Concept Map

Prerequisites​

  • You can log in to Witboost.
  • You can view and edit the descriptor of your project.

Overview​

Linking your project to the Business Concept Map, once it gets published as product in the Marketplace, allows Marketplace users in your organization to discover it through the business terms that describe what the product is about.

This helps it appear in the right business context and makes it easier for others to understand and find it.

Why integrate?​

When you associate your project with Business Concepts:

  • it becomes discoverable through business terminology
  • users can find it without knowing its technical name
  • it appears next to related concepts in the Business Concept Map
  • business meaning becomes clear and consistent across teams

This strengthens both findability and governance.

Step by step​

  1. Identify the relevant Business Concepts

    Your organization defines a set of Business Concepts that represent important business terms such as:

    • Customer
    • Compensation
    • Predictive Maintenance
    • Employee Performance
    • Liquidity Risk

    Select the concept(s) that best describe your project from those you see in the Business Concept Map.

  2. Add the concepts to the descriptor

    Your organization defines, through configuration, one or more descriptor paths where Business Concepts can be assigned.

    These paths may appear anywhere inside the descriptor, including:

    • at the top level of the descriptor
    • inside any of the components listed under the components: section

    This flexibility allows Business Concepts to be associated either with the project as a whole or with specific components that contribute to it.

    note

    If you're unsure which paths are configured by your organization, ask your platform team. They can confirm where Business Concepts should be added in the descriptor.

    Default paths (they could have been overridden by the configurator):

    • tags.tagFQN
    • businessConcepts.tagFQN
    • dataContract.schema.tags.tagFQN
    • dataContract.schema.businessConcepts.tagFQN

    Regardless of where the concepts are placed, the Business Concept Map always shows the project itself.

    Components are not shown individually; all concepts found in the configured paths — whether on the project root or within its components — are aggregated and linked to the project in the map.

    tip

    To integrate your project with the Business Concept Map: add one or more Business Concepts to any of the configured paths defined by your organization.

    Choose the concepts that best reflect the business meaning of your project or its components.

    Example​

    Suppose your organization configures the following path as a source of Business Concepts: tags.tagFQN.

    This means that any tagFQN found under a tags: list, whether on the project root or inside component descriptors, will be interpreted as a Business Concept.

    A project descriptor may look like:

    name: customer-payroll-stats
    description: Payroll aggregates and monthly metrics for active employees.

    tags:
      - tagFQN: Payroll
        source: Tag
        state: Confirmed
      - tagFQN: Compensation
        source: Tag
        state: Confirmed

    components:
      - name: payroll-input
        tags:
          - tagFQN: Employee Data
            source: Tag
            state: Confirmed

      - name: payroll-metrics
        tags:
          - tagFQN: Payroll Metrics
            source: Tag
            state: Confirmed

    In this example, all Business Concepts found in the descriptor, whether on the project root or inside components, are aggregated:

    • Payroll
    • Employee Data
    • Payroll Metrics

    In the Business Concept Map:

    • the project appears once, under each of these concepts
    • components do not appear independently
    • the project is discoverable whenever any of the associated concepts are explored

  3. Publish your project

    Once the project is deployed and published in the Marketplace as a Product:

    • the assigned Business Concepts are detected
    • the Product is automatically associated with those concepts
    • the Product becomes visible in the Business Concept Map under each assigned concept

    You do not need to perform any additional configuration.

Best Practices​

  • Select specific Business Concepts rather than very broad ones.
  • Review concept definitions to ensure accurate alignment.
  • Use multiple concepts only when they truly represent your project.
  • If unsure which concept applies, consult your governance team or data stewards.

Result​

When the integration is complete:

  • Your project appears in the Business Concept Map.
  • Users exploring a concept can see your project immediately.
  • Your project becomes easier to discover through business context.

This allows Data Consumers to navigate from what they understand (business terms) to what they need (your Product).