---
sourceDocument: Australia Telecommunications, Media, and Technology
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/telecom-media-technology

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Telecommunications, Media, and Technology

ft:clusterId :

    - telmt

bundleId :

    - telmt

workflow :

    - Customer and Industry


---

# Specification versions

# Creating and publishing specification versions {#ariaid-title1}

Release version: Australia  
Updated April 14, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Creating and publishing specification versions

This process enables product catalog managers to create and publish updated versions of product, service, or resource specifications within a technical product catalog.
These catalogs define the offerings available to customers and evolve over time to reflect engineering improvements and market-driven changes in fit, form, function, pricing, and capabilities.
By maintaining versioned specifications and product offerings, you ensure that sales agents use the most current information to promote upgraded or complementary products effectively.
Show full answer Show less  

## Creating Specification Versions

When creating a new specification version, you:

* Assign a version number to affected specifications or product offerings.
* Update characteristics, characteristic options, specification relationships, decomposition rules, quantity mappings, and attribute propagation rules to reflect engineering changes.
* Create new specification relationships and attribute mappings as needed.

You can then create and publish a corresponding product offering version, and retire or archive outdated specifications and offerings.

## Data Copying and Validation

Upon creating a new version from an existing published specification, the system automatically copies key fields such as category, type, description, product code, and cost details, while resetting external version information. It populates version-specific fields like version number, display name, initial and previous version identifiers, and duplicates associated characteristics, options, relationships, and rules.

Publishing a new specification version triggers validations to ensure all rules and references are consistent with the updated characteristics. Errors may occur if referenced specifications or characteristics are invalid or outdated.

## Resolving Validation Errors

Common validation errors involve invalid specification versions or characteristics in relationships, decomposition rules, attribute mappings, and propagation rules. To resolve these:

* Update source specifications to current versions in Specification Relationships and Attribute Propagation forms.
* Review and correct or remove invalid characteristics or characteristic options in Decomposition Rules and Attribute Mappings forms.

Only after all validation errors are resolved can the new specification version be successfully published.  
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. Agents can then sell more expensive, complementary, upgraded, or related products to your customers.

## Creating specification versions for use in product offerings {#creating-publish-specification-versions-somt__section_tq4_tl2_2tb}

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
   {#creating-publish-specification-versions-somt__ul_zrh_5dd_5tb}  
   Note:  
   To learn more, see [Create and publish a specification version](https://www.servicenow.com/docs/gzkLb6geOombkkNUhM~01w "Create and publish a version of an existing specification in a Published state so that you can offer an improved version of it to your customers in your product catalog.").
3. Create a product offering, and then publish it when you update your product catalog. To learn more, see [Create and publish a product offering version](https://www.servicenow.com/docs/BBrzeS09l2mA1f2BPg3pKA "Create and publish a version of an existing product offering in a Published state so that you can offer an improved version of it in your product catalog.").
4. Retire or archive old or unused specifications, and product offerings. To learn more, see [Retiring and archiving versioned specifications](https://www.servicenow.com/docs/cc4LE5LaS4ylKxnMU4o4yw "When a published specification or product offering is no longer being used, you can retire it. A retired version stays in the operational tables, but you can't use it in a product offering or create specification versions from it. To remove a retired version from the operational tables, archive it. Archiving doesn't permanently delete the version.").
{#creating-publish-specification-versions-somt__ol_dsz_5k2_2tb}

## Updates and validations that are performed when you create and publish a specification version {#creating-publish-specification-versions-somt__section_qw5_mmt_2tb}

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
   {#creating-publish-specification-versions-somt__ul_eql_v5t_2tb}
2. Blanks out the External Version field.  
   Note:  
   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.
   {#creating-publish-specification-versions-somt__ul_wxc_r53_ptb}
4. Copies the associated characteristic and characteristic options. To learn more, see [Create the characteristics and characteristic options for your product offerings](https://www.servicenow.com/docs/access?context=order-mgt-characteristics&version=australia&pubname=australia-order-management&ft:locale=en-US).
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.  
   Note:  
   To learn more about these rules, see [Create specification relationships, quantity mapping, and decomposition rules for Order Management](https://www.servicenow.com/docs/access?context=order-mgt-specification-rels&version=australia&pubname=australia-order-management&ft:locale=en-US).
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 .
{#creating-publish-specification-versions-somt__ol_kyt_kst_2tb}

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 modify the characteristics referenced by the other rules that are associated with the new specification version. If an error occurs, a message similar to this example appears.

## Copied rules validation errors {#creating-publish-specification-versions-somt__section_t2m_nmk_bjc}

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.{#creating-publish-specification-versions-somt__table_snw_zpt_2tb__entry__2}

| Error | Resolution actions |
|-|-|
| Invalid specification version in the specification relationship. | Update the source specification version to the current version: 1. Select Specification Characteristics. 2. Update the Source Specification field in the Specification Relationships form. {#creating-publish-specification-versions-somt__ol_p4m_yzt_2tb} |
| Invalid specification versions in the decomposition rule. | Update the source specification version to the current version: 1. Select Specification Relationships. 2. Update the Source Specification field in the Specification Relationships form. {#creating-publish-specification-versions-somt__ol_jwc_g15_2tb} |
| Invalid characteristic in the decomposition rule. | Update or remove the invalid characteristic in the Decomposition Rules form: 1. Select Specification Characteristics. 2. Update or remove any invalid characteristics. {#creating-publish-specification-versions-somt__ol_wgl_415_2tb} |
| Invalid characteristic options in the decomposition rule. | Update or remove the invalid characteristic options in the Decomposition Rules form: 1. Select Specification Characteristics. 2. Update or remove any invalid characteristic options. {#creating-publish-specification-versions-somt__ol_dsc_r15_2tb} |
| Invalid characteristic options in the quantity rule. | Update or remove the invalid characteristic options in the Attribute Mappings form: 1. Select Attribute Mappings. 2. Update or remove any invalid characteristic options. {#creating-publish-specification-versions-somt__ol_nxy_r15_2tb} |
| 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. Select Attribute Mappings. 2. Update or remove any invalid characteristics. {#creating-publish-specification-versions-somt__ol_ag4_cb5_2tb} |
[Table 1. Copied rules validation errors and resolution actions]

{#creating-publish-specification-versions-somt__table_snw_zpt_2tb}