---
schema_version: "1"
id: 300248188d9b6d71af14d6c4c67da3b3d2abdf1130dee0d8cf007c867aadbf6c
title: Settings to Support Canceling Orders
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_settings_to_support_canceling_orders.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_settings_to_support_canceling_orders.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: df1a3aead723e877b3f8b98495874e448b98a5b8a509d481e04495dd733a0d2e
description: When installing or upgrading CME, you can create a remote site setting to support such actions as canceling orders, and accessing the streaming API. Once you have created the remote site setting, you do not need to do it again for subsequent CME upgrades.
products:
  - Communications
  - Media
  - Energy and Utilities
release: "264"
---
# Settings to Support Canceling Orders

When installing or upgrading CME, you can create a remote site setting to support such actions as canceling orders, and accessing the streaming API. Once you have created the remote site setting, you do not need to do it again for subsequent CME upgrades.

There are three parts that support canceling orders:

- A streaming channel, which is automatically installed.
- A remote site setting, which you must add.
- Interfaces and implementations, specifically:
    
    - XOMSupplementalOrderLifeCycle implementation: Before CME Winter '20, this was the only implementation to handle the full life cycle of a supplemental order when only Cancel was implemented. There was no unified interface to submit a simple order and assetize it.
        
        For CME Winter '20, the OdinAPIHandler (ODIN) interface was introduced to deal with the life cycle for any kind of order (such as Simple, MACD, or Supplemental) between CPQ and Order Management (OM). In OM Standard, this interface was directly implemented with XOMOMStandardOdinAPIHandler instead of using the default  OdinStandardAPIHandler. This release also kept the other implementation, XOMSupplementalOrderLifecycleImpl, to deal with Supplemental order calls during cancellation.
        
        As of CME Spring '20, only the OMOMStandardOdinAPIHandler is used and XOMSupplementalOrderLifecycleImpl is no longer used. OM Plus uses the standard implementation to deal with extra interfaces, such as SendSubmitToOM, SendFreezeToOM, SendUnfreezeToOM, and OdinSubmitOrderExtraFields.
    - SupplementalOrderService interface: This interface is used within the OdinAPIHandler interface, specifically within the OdinAPIAutoAssetizeHandler implementation. When the `preValidate` API or `unfreezeOrder` API call is made from the client, the call uses the implementation configured for the OdinAPIHandler. If OdinAPIAutoAssetizeHandler is the active implementation of the OdinAPIHandler interface, then it internally calls the SupplementalOrderService interface. The only out-of-box implementation for SupplementalOrderService is SupplementalOrderServiceImplementation.
    - XOMSupplementalOrderLifecycleImpl implementation: This interface is used from SupplementalOrderServiceImplementation. When the OdinAPIHandler interface is configured with OdinAPIAutoAssetizeHandler as the active implementation, any call to the preValidate API or unfreezeOrder API call is handled through SupplementalOrderService. The only out-of-box implementation for SupplementalOrderService is SupplementalOrderServiceImplementation. This interface (XOMSupplementalOrderLifeCycle) helps SupplementalOrderServiceImplementation freeze and unfreeze orders.
    - XOMSupplementalOrderLifeCycle interface: This implementation is for the XOMSupplementalOrderLifeCycle interface. It provides a stub for the freezeOrder and unfreezeOrder API calls. This interface is invoked only when the OdinAPIHandler interface has OdinAPIAutoAssetizeHandler as the active implementation and SupplementalOrderService interface has SupplementalOrderServiceImplementation as the active implementation.

To support canceling orders, you must add your Salesforce org base URL to the remote site settings.

To create a remote site setting:

1. From Setup, in the **Quick Find** box, enter Remote Site.
2. Click **Remote Site Settings**.
3. Click **New Remote Site**.
4. On the **Remote Site Edit** page, enter the following information:
    
    - **Remote Site Name** is StreamingAPI.
    - **Remote Site URL** is the base URL of the CPQ cart. To determine this URL, go to an order and navigate to the CPQ cart, which will have a URL such as `https://cmt-106-vlocity-cmt.na72.visualforce.com/apex/hybridcpq?id=8011H000FEZ84RA5`. It should include the namespace. The value for the corresponding Remote Site URL is `https://cmt-106-vlocity-cmt.na72.visual.force.com`.
        
        For new Installations, the StreamingAPI should be set as the Remote Site Name.
        
        You need to switch to Salesforce Classic before you invoke the Cart to see that version of the URL.
5. Do not select Disable Protocol Security. Leave it set to false.
6. Select **Active**.
7. Click **Save**.