Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Order Management Guide Addendum for Communications > Setting Up Network Ordering > About Cross-Network ValidationIn addition to validating the network across products in the current order, network order entry validates the newly ordered products across the customer's existing assets and open orders. This is called cross-network validation, and it allows the Siebel application to validate that the network and network elements in the current quote or order are compatible with other networks that this customer has. Cross-network validation validates the network and network elements in the current quote or order along with the network and network elements associated with the current network, using the compound validation rules specified in administration screen. The two networks are linked using a configurable user property called ValidateFieldName NOTE: You might have to install and configure a product patch to use cross-network validation. For more information, see the documentation for the patch. Example of Cross-Network ValidationHere is a simple example of cross-network validation. The product administrator has defined the products in Table 138 with compound product validation rules. After purchasing these products, the customer has assets with the following structure: Now customer wants to add another network with additional nodes and link the existing network nodes with the new network nodes, so the customer creates a quote or order with the following elements: - Connection X (Port C to Port A). The ValidateFieldName user property is used to configure the name of the field that connects two networks. In this example, if cross-network validation is enabled, when the sales representative validates Network 2, then Network 1 is also validated. Cascade Deletion with Cross-Network ValidationWhen a node is disconnected, all associated connections are included in the disconnect order or disconnect quote based on the account type. When cross-network validation is used, cascade deletion on a node can also trigger deletion of connections belonging to other networks. Using the example in this topic, disconnection of Port A triggers the disconnection of Connection X. Similarly, disconnection of Port C triggers the disconnection of Connection X. |
![]() ![]() |
Siebel Order Management Guide Addendum for Communications | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |