Creating and publishing specification versions

  • Freigeben Version: Australia
  • Aktualisiert 12. März 2026
  • 4 Minuten Lesedauer

    • As a product catalog manager, you can create and publish the specification versions that list the improved products and services that you can offer to your customers in a technical product catalog.

    Your product catalogs define the products, services, and resources available to your customers so they can decide what to purchase from you. Your catalog items will continue to evolve over time to accommodate the changes that are related to how your items are sold, configured, and delivered to your customers. Typically, these changes are related to engineering improvements that make the products, services, and resources more marketable and appealing to your customers. The changes usually are to the fit, form and function, characteristics, and characteristic options, and specification relationships of your catalog items. For example, a home internet product may evolve over multiple revisions to support changes that are related to pricing and increased internet speeds.

    By creating new specification and product offering versions for your products, you enable your agents to work with the latest versions of your product and service offerings when they sell more expensive, complementary, upgraded, or related products to your customers.

    Creating specification versions for use in product offerings

    As a product catalog manager, you do the following actions when you create a version of a specification for use in a product offering:

    1. Create and assign a version number in each of the product, service, or resource specifications or product offering records that are affected by the changes.
    2. Create the required specification relationships, decomposition rules, and attribute mappings for each specification in the new version. As a product catalog manager, you update the following information to reflect the engineering changes that were made to the associated specifications:
      • Characteristics
      • Characteristic options
      • Specification relationships
      • Decomposition rules
      • Quantity mappings
      • Attribute propagation rules
      Hinweis:
      To learn more, see bf5de20e1f5fbc744bbe7b1638555b41759475be.dita.
    3. Create a product offering, and then publish it when you update your product catalog. To learn more, see 1f08de72230e2f86c4ee6372eb82bc1bb4157527.dita.
    4. Retire or archive old or unused specifications, and product offerings. To learn more, see 96c26780aa2f82a4edcdd41b03ee5ee6e4439a05.dita.

    Updates and validations that are performed when you create and publish a specification version

    When you create a version for a currently published specification, the system copies the following data into, or populates, the new specification record as follows:

    1. Copies the following fields with these basic specification details:
      • Category
      • Type
      • Start and End date
      • Description
      • External ID
      • Product code and Product line
      • Cost to Company
      • Composite
      • Installation Required
      • Location-specific
    2. Blanks out the External Version field.
      Hinweis:
      The External ID and External Version fields don't appear on the specification forms by default but can be added by changing the form layouts.
    3. Populates the following fields with the detailed information that you enter for the new specification version:
      • Version. The next incremental number appears.
      • Display Name. The display name is the system-assigned concatenation of the specification name and its current version number. You can overwrite this field.
      • Initial Version. The name of the base version of the specification appears but can't be changed.
      • Previous Version. The name of the specification is as it was in the previous version.
    4. Copies the associated characteristic and characteristic options. To learn more, see d8acf7ba6379ad854fb858b4452e2b91cda53db3.dita.
    5. Copies the associated specification relationships, attribute mapping, decomposition rules, and quantity mappings when you use extension point scripts. When copied, the source specifications in the associated specification relationship and decomposition rule records are automatically updated to the current versions of the source specifications. For example, if an SD-WAN Edge Device was the source specification in these records, and you created a new SD-WAN Edge Device version 2, that becomes the new source specification.
      Hinweis:
      To learn more about these rules, see aa7a7b1e352b0a3ea86aeee206275ac4d1ff79a6.dita.
    6. Copies the associated quantity mappings and attribute propagation rules. The source specifications in the quantity mappings and attribute propagation rules are also updated to the current versions. To learn more about these rules, see e6b772fa216ed4b1bc1bacf0dec7ac6bcf74f26e.dita.

    When you publish the updated specification version, the ServiceNow AI Platform® performs validations on your edits. These validations ensure that all rules are valid with the characteristic and characteristic options that are available for the new specification version. An error might occur if you inadvertently remove or change the characteristics or characteristic options that are referenced by the other rules that are associated with the new specification version. If an error occurs, a message similar to this example appears.

    Abbildung : 1. Copied rules validation errors
    Message showing a list of all the validation errors and their details. To more information, refer to the following description.

    You can publish a new specification version only after you resolve all errors. This table contains some possible validation errors that you may see and the actions you can take to resolve the issue.

    Tabelle : 1. Copied rules validation errors and resolution actions
    Error Resolution actions
    Invalid specification version in the specification relationship. Update the source specification version to the current version:
    1. Click Specification Characteristics.
    2. Update the Source Specification field in the Specification Relationships form. For example, if you're creating SD-WAN Edge Device version 2, and it contains the previously published SD-WAN Edge Device version 1, update the field accordingly.
    Invalid specification versions in the decomposition rule. Update the source specification version to the current version:
    1. Click Specification Relationships.
    2. Update the Source Specification field in the Specification Relationships form.
    Invalid characteristic in the decomposition rule. Update or remove the invalid characteristic in the Decomposition Rules form:
    1. Click Specification Characteristics.
    2. Update or remove any invalid characteristics.
    Invalid characteristic options in the decomposition rule. Update or remove the invalid characteristic options in the Decomposition Rules form:
    1. Click Specification Characteristics.
    2. Update or remove any invalid characteristic options.
    Invalid characteristic options in the quantity rule. Update or remove the invalid characteristic options in the Attribute Mappings form:
    1. Click Attribute Mappings.
    2. Update or remove any invalid characteristic options.
    Invalid specification version in the attribute propagation rule. Update the Source Specification field in the Attribute Propagation form to the current version.
    Invalid characteristic in the attribute mapping rule. Update or remove the invalid characteristics in the Attribute Mappings form:
    1. Click Attribute Mappings.
    2. Update or remove any invalid characteristics.