--- sourceDocument: Australia Sales and Order Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management Release : - australia ft:locale : - de-DE ft:publication_title : - Australia Sales and Order Management ft:clusterId : - omgmt bundleId : - omgmt workflow : - Customer and Industry --- # Create and publish a specification version # Create and publish a specification version {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 Minuten Lesedauer 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. ## Vorbereitungen Before you can create a version of a specification, an initial base version of the specification must exist and already be published. The information that you supply for a new version is the same as what you entered for an initial base version, but with some important differences. To learn more, see [0f03ade088fed750d8bed0be86597769252c933c.dita](https://servicenow-prod.fluidtopics.net/186f8_wuEI3mkhxyaddfyw "Create and publish a base version of a product specification. A product specification defines all the product options that apply to a customer-facing product you sell, and designates how to fulfill these options. It contains information such as the product description, pricing, eligibility, and product options."). Role required: sn_prd_pm.product-catalog_manager ## Warum und wann dieser Vorgang ausgeführt wird You create versions of service and resource specifications in the same manner as you do a resource specification. ## Prozedur 1. Navigate to AllProduct Catalog ManagementProduct Specifications. 2. In the Product Specifications list, select the product specification that you want to create a version for. 3. On the form, click Create New Version and then fill in the fields. The manner in which you create a version of a specification is similar to how you created its initial version, with the differences that are explained in the following table. {#create-publish-new-version-specification__table_pyl_fvq_4nb__entry__2} | Field | Description | |-|-| | Name | Name of the new product specification. If the name of the item for the new version differs from the previous version, you can enter a new name. For example, if the name of the item is SD-WAN Security, override it if you want a new name for the new version. | | Version | Version number that is assigned to a specification: * When you create the initial version, 1 appears in this field, and can't be changed. * When you create subsequent versions of the specification, the next incremental number appears in this field after you click Create New Version. For example, 4 appears in this field if 3 was the previous version number. {#create-publish-new-version-specification__ul_fld_dlf_2tb} | | Display Name | Displayed name that appears for the specification in the ServiceNow AI Platform when this version of the specification is in effect. * When you create the initial, or base version of the specification (for example, version 1), you must enter free-form text, which is usually the name of the specification, into the field. * When you create versions of the specification, a system-assigned concatenation of the specification name and its current version number appears, but can be overwritten. For example, SD-WAN Edge Device v2 appears in this field when: * SD-WAN Edge Device is the name of the specification. * Version 2 is the current version of the specification. {#create-publish-new-version-specification__ul_sx4_bss_2tb} {#create-publish-new-version-specification__ul_rx4_bss_2tb} | | Initial Version | Name of the base version of the specification that appears but can't be changed. | | Previous Version | Name of the previous version of the specification. For example: * When you create the initial version of the specification (for example, version 1), this field is empty. * When you create a version (version 2) with a slightly different name, the name of the specification at its initial creation appears here. * When you create a subsequent version (version 3), the name of the specification as it was at version 2 appears here. {#create-publish-new-version-specification__ul_dmc_zjc_dtb}You can't change this field. | [Tabelle : 1. Product specification form] {#create-publish-new-version-specification__table_pyl_fvq_4nb} Hinweis: For information about the remaining field descriptions, see [Field descriptions for product catalog forms in Order Management for Telecommunications and Media](https://servicenow-prod.fluidtopics.net/zB6KByVNGxsL_C~B4B~T8w#fields-product-specifications-form "The Product Specifications form enables you to create and publish a product specification to define all the products options that apply to a product."). 4. To reflect the engineering changes that were made to the physical product, update the specification relationships, decomposition rules, quantity mappings, and attribute propagation rules as follows: 1. To update the characteristics and characteristic options that are associated with your specification, use the Specification Characteristics related list. To learn more, see [696b1f06852a29ca0015b3bc711589daafdaadcb.dita](https://servicenow-prod.fluidtopics.net/oDNMqUOltE~HeDVHNGHx5w#order-mgt-specification-rels "Create the specification relationships and optional decomposition rules that define the associations between the product, service, and resource specifications for a product that you offer. These relationships impact how an order is fulfilled for a customer."). 2. To update the specification relationships and accompanying decomposition rules, use the Specification Relationships related list. To learn more, see [696b1f06852a29ca0015b3bc711589daafdaadcb.dita](https://servicenow-prod.fluidtopics.net/oDNMqUOltE~HeDVHNGHx5w#order-mgt-specification-rels "Create the specification relationships and optional decomposition rules that define the associations between the product, service, and resource specifications for a product that you offer. These relationships impact how an order is fulfilled for a customer."). 3. To update attribute mappings, use the Attribute Mappings related list. To learn more, see [9eb6eb97c8a4daf06b9117a49715bfe59b35d310.dita](https://servicenow-prod.fluidtopics.net/84jvi4jxFO8j_7AIDMwDhw "By defining attribute-mapping rules between two specifications in the product catalog, your fulfillment agents can access all relevant characteristic values in your product, service, and resource orders."). 4. To create a product offering from the specification, navigate to the Product Offerings related {#create-publish-new-version-specification__ol_xt2_gwt_2tb} 5. When you finish creating the specification version, do one of the following actions. | Action | Description | | Publish | Publish the draft specification so that you can use it in a product catalog as follows: * When you publish it, its state changes from Draft to Published. * After you publish a specification, you can't change or delete it, unless you create a version for it. {#create-publish-new-version-specification__ul_y4k_4ts_2tb} | | Update | Update the specification with the new data that you added, but do not publish it for use in a product catalog. | | Copy | Copy the data in this specification so that you can create a specification from it. For example, you can use the Copy function if you want to create a base version specification that is similar to SD-WAN Edge Device v2, but with a separate version track. When you use the Copy function, it creates a base version specification, and sets the values in these fields: * Version: 1 (base version) * Initial Version: SD-WAN Edge Device v2 * Previous Version: blank {#create-publish-new-version-specification__ul_jzn_l42_5tb} | |-|-| {#create-publish-new-version-specification__choicetable_product_offering} Hinweis: To learn more about the validations that are performed when you publish a new specification version, and how to resolve any reported errors, see the section about validations in [f83145089649af8ef69fec90f2f7108bdb527ca6.dita](https://servicenow-prod.fluidtopics.net/Br_U7HX2Qq4L32YWHolrig "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."). {#create-publish-new-version-specification__step-initial-base-product-offering-actions} {#create-publish-new-version-specification__step-initial-base-product-offering-actions} **Zugehörige Tasks** * [0f03ade088fed750d8bed0be86597769252c933c.dita](https://servicenow-prod.fluidtopics.net/186f8_wuEI3mkhxyaddfyw "Create and publish a base version of a product specification. A product specification defines all the product options that apply to a customer-facing product you sell, and designates how to fulfill these options. It contains information such as the product description, pricing, eligibility, and product options.") * [ca32b015fe6fb38499285c1f0b0cb443cefdecef.dita](https://servicenow-prod.fluidtopics.net/_qKqxa6RCBnzh94djewfeA "Create and publish a base version of a service specification. A service specification defines all the service options that apply to a customer-facing product you sell, and designates how to fulfill these options.") **Zugehörige Verweise** * [Product catalog data model and catalog versioning](https://servicenow-prod.fluidtopics.net/cgdmqs8Lvt8aShp_YUbCaA#order-mgt-product-data-model "Technical product catalogs have a framework for defining the technical products, services, and resources that you want to sell to your customers.")