---
schema_version: "1"
id: d8da407008b299fb461d2d27fb35522fbe5d498753b71671056ec82d51d3f240
title: "Example: A DSL Order"
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_t_examplea_dsl_order_235370.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_t_examplea_dsl_order_235370.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 09f072b501246c3c53cb0c9fd7db53da0e21091c009a32b0fb7ba7fe4ef0ddf2
description: Let's say that there's an order to activate a DSL service. Doing so requires an inventory system to reserve a port. Later, the port value must be sent to an activation system.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# Example: A DSL Order

Let's say that there's an order to activate a DSL service. Doing so requires an inventory system to reserve a port. Later, the port value must be sent to an activation system.

During orchestration of the order, the following things happen:

1. A callout makes a port reservation API call to the inventory system.
2. The inventory system returns a specific port value, and a success response.
3. Order Management stores the port value on the order (which it will use later), the callout is marked complete, and the workflow continues.
4. When the order is ready for activation on the network, a second callout sends the saved port value to the activation system.
5. The activation system returns a success response, the callout is marked complete, and the workflow continues.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-order_management-264-0-0-production-enus/c2040b01-aade-4ba7-8a7d-d7cd745d5c8c/images/icon_note.png)

Note

Once a callout is sent, you can view the callout payload and any response in the **Interaction Details** section of the **Details** page of the orchestration item that sent the callout.