Defining mappings for attribute value propagation to domain orders

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

    • 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.

    Attribute mapping overview

    Orders, for example telecommunications orders, contain many characteristics and characteristic values that are populated at different stages of the order life cycle. Order Management automatically propagates and transforms the characteristics and characteristic values throughout the order fulfillment process. This automatic propagation of attributes across the product, service, or resource orders help to improve your operational efficiency and eliminate errors in the fulfillment process.
    Hinweis:
    Attribute values are another name for order characteristic values.

    When value attribute values are assigned and how they're used

    Orders contain many characteristics and characteristic values that are populated at different stages of the order life cycle. Multi-site enterprise orders contain various attributes that are related to customer, product, service, and resource information. The ServiceNow AI Platform populates these attributes with the corresponding values at the different stages of the order life cycle. To learn more, see Use case scenario.

    The ServiceNow AI Platform decomposes orders and order line items into various suborders (product, service, and resource orders) and assigns them to different user groups and users. Different user groups then work with the various suborders to complete the required fulfillment tasks for a given order.

    Catalog-driven attribute mapping and value propagation

    The order fulfillment flow needs prior information on how specification characteristics are mapped and associated so that the characteristics are propagated from one domain order to another domain order. If you're a product catalog manager, you can define rules-driven attribute mappings between and among selected product, service, and resource specifications. When you define attribute mappings, validations run to verify that they're unique, don't conflict with each other, or conflict with defined specification relationships and decomposition rules.

    To learn more about specification relationships, see aa7a7b1e352b0a3ea86aeee206275ac4d1ff79a6.dita.

    The Order Management application executes attribute mappings during the order fulfillment process and sets and propagates order characteristic values across the various suborders.

    The order fulfillment process evaluates the attribute-mapping rules that you define. The attribute values are propagated from the domain orders that are associated with the source specification to the domain orders that are associated with the target specification.

    With catalog driven rule-based attribute propagation, your fulfillment agents have all the relevant and correct information that they require to work effectively on order tasks. The attribute-mapping functionality reduces errors and improves efficiency in the order fulfillment process as follows:
    • Without rules-driven attribute mapping, your users have to assign the attribute values manually, which can be error-prone and time-consuming.
    • These values propagate to lower domain orders and are used for inventory creation, service activation, and account and billing updates. Fixing an error takes a significant amount of effort and time for your users when these values are manually assigned.
    • Attribute mappings promote the proper flow of crucial data through the associated domain orders. This mapping makes consistent data available to users with different roles when they're processing an order.

    Use case scenario

    Let's look at how an attribute-mapping rule is defined. For example, when a customer orders an SD-WAN Service Package, the selected characteristics for the SD-WAN edge device drive the generation of the associated product, service, and resource orders. By maintaining the correct attribute relationships in the source and target specifications, you ensure that the corresponding data values are correctly set for the associated domain orders. The following diagram shows the SD-WAN product model.
    Abbildung : 1. SD-WAN product model
    Infographic displaying the relationship between product offering, product specification, service specification, and resource specification. For a description, refer to the text that follows.
    The following diagram shows the mapped relationships between the selected characteristics in the source SD-WAN edge device specification and the services that result from their selection:
    • If a customer selects Premium Routing, the SD-WAN routing characteristic is defined with the Open Shortest Path First (OSPF) Routing Protocol characteristic option.
    • If a customer selects Premium SD-WAN Optimization, the customer gets the SD-WAN Optimization Service with Secure Socket Layer (SSL) Optimization as the result.
    • Common Platform Enumeration (CPE) type selections for the SD-WAN edge device specification define the CPE type for the Customer Premise SD-WAN router specification.
    Abbildung : 2. Attribute mapping relationships for an SD-WAN edge device
    Mapped relationships between selected characteristics in the source SD-WAN edge device specification and services resulting from selection. For the text description, refer to the following text.
    When you create an attribute mapping rule for these relationships, it results in the following record.
    Abbildung : 3. Attribute mapping for the SD-WAN edge device product specification
    Table showing record details of the SD-WAN edge device with its details.