Understand Asset Types and Service Catalogs

Learn how schemas and managed catalog data work together before you create either one.

Lifecycle from a draft Asset Type through catalog setup, publication, and Asset verification.

An Asset Type defines the structure of an asset record: its sections, fields, dependencies, and whether a field uses managed catalog data. A Service Catalog provides those managed choices and their relationships.

Use this order

  1. Create a custom Asset Type and keep it as a draft.
  2. Configure its sections, fields, dependencies, and catalog support.
  3. Select the draft Asset Type in Service Catalog.
  4. Add the needed catalog entries, models, modules, software, specifications, attributes, and compatibility.
  5. Save and verify the catalog.
  6. Publish the Asset Type.
  7. Create or edit an asset and verify its catalog-backed selections.

Publishing can make a custom schema read-only. Treat publication as a release decision, not a routine save.

What belongs in each place

NeedConfigure it in
A new kind of assetAsset Types
A section or field on that assetAsset Types
A field dependencyAsset Types
An approved manufacturer or provider choiceService Catalog
Models, modules, or softwareService Catalog
Specifications and attributes tied to catalog entriesService Catalog
Which catalog items work togetherService Catalog compatibility

Plan a small first version

Start with the fields needed for one real workflow. Use familiar names and assign an owner.

Before publication, test the draft with non-customer sample data.

Related tasks

Get help

Email [email protected] and include:

  • Company, affected user, page URL, timestamp, and time zone
  • Draft Asset Type name or ID
  • The model you are trying to represent

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


Did this page help you?