Add catalog entries and compatibility

Add supported catalog records and define which models, components, or software work together.

Outcome: Build the managed choices needed by a draft Asset Type and verify their compatibility relationships.

For: Customer administrators and data model owners
Permission: update service_catalog
Time: 15–30 minutes
Changes made: Adds or changes shared catalog entries and compatibility

If you're stuck

  • Confirm the selected Asset Type is the intended customer draft.
  • Add and save the parent entry before trying to add its Model, Module, or Software child.
  • Search by canonical name and provider ID before creating a near-duplicate.

Before you start

  • Select the intended custom Asset Type and confirm its status is Draft.
  • Agree on naming conventions and sources.
  • Start with one complete manufacturer or provider family.
  • Confirm which parent record is required before adding a Model, Module, or Software item.

Field and relationship guide

Entry or settingPurposeRequired contextVerification
Provider or ManufacturerTop-level catalog identityCanonical name and source referenceAppears once at the catalog root
ModelProduct or offering under a parentSaved Provider or ManufacturerAppears under the intended parent
Module or SoftwareComponent or software choiceSupported saved parentAppears under that parent, not at the catalog root
SpecificationStructured technical characteristicEntry whose schema accepts that specificationReopens with the saved value and unit
AttributeAdditional managed characteristicEntry and supported attribute keyReopens on the intended entry
CompatibilityRestricts valid combinationsBoth related catalog entries must already existDependent Asset field shows only approved choices

Add entries

  1. Open Administration → Service Catalog and select the draft Asset Type.
  2. Select Add.
  3. Choose an available top-level type such as Manufacturer, Provider, Carrier, or Carrier Loop.
  4. Enter its name, description, and approved custom data.
  5. Save the entry.
  6. Select the saved Provider or Manufacturer that owns the product, then add Model if that parent exposes the action.
  7. Under the required manufacturer context, add Module or Software where supported.
  8. Add the available specifications and catalog attributes.
Service Catalog item showing an example service name, description, prefix, routing type, scope, and update action.
  1. Save after each coherent group of changes.

Expected result: The hierarchy shows each entry under the intended parent with its saved details.

If an option is absent, first select the parent that makes the child type valid. Do not create a differently named substitute.

Define compatibility

  1. Open the catalog entry that provides compatibility settings.
  2. Search for the supported models or components.
  3. Select only combinations approved for the customer workflow.
  4. Save the entry.
  5. Reopen it and confirm the selected compatible items remain.

Expected result: Asset fields can present compatible downstream choices based on the selected parent value.

Check your result

Use a documentation-only asset after the catalog is saved. Select the parent catalog value and confirm the expected compatible options appear without near-duplicates.

Undo this change

Remove an incorrect compatibility selection and save again. Before editing or removing a catalog record, confirm whether it is used by any asset or dependent entry.

Learn and continue

Next steps

Get help

Email [email protected] and include:

  • Company, affected user, page URL, timestamp, and time zone
  • Asset Type ID, entry IDs, and expected compatibility
  • Reproduction steps and the exact error

Never send passwords, credentials, tokens, or secret values.


Did this page help you?