Orchestration Item Types: Auto Task

An auto task processes internal data and automatically executes by invoking an Apex class that's associated with the orchestration item.

Order Management supports the following item implementations:

• Technical Assetization: A common use of an auto task is to create assets as one of the last steps of order processing. Order Management provides an out-of-the-box item implementation called Assetize and an Apex class called XOMAutoTaskAssetizer to perform this function as part of the managed package.

  Technical assetization means storing the output of decomposition to the technical inventory in Order Management. This is different from commercial assetization, which stores the commercial products selected by the customer in Salesforce, creating a snapshot of the products or services to which the customer has subscribed.

  In Order Management, you can use an Assetize auto task from a commercial product or a technical product to create assets and inventory items.

  You don't always need to persist technical products in inventory. Sometimes, you only need to create a decomposition rule to generate a payload to send to an external system. In this case, the technical product is more of an event than a product you need to keep track of in inventory. For example, a technical product could be a one-off event like sending a thank you email or shipping a promotional T-shirt as part of an offer. While you may want to create a decomposition to ease the interaction with the shipping system, you do not need to keep that object in the inventory. To view the inventory items, you can add the Inventory Items-related list to the Account layout. The items are stored in the vlocity_cmt__InventoryItem__c table. The name of the inventory item is provided by the LineNumber field from the Fulfillment Request Line of the order that created the inventory item.

  In Order Management, use the Not Assetizable check box when creating a technical product to specify whether or not a technical product should be assetized within the Order Management technical asset tables. To assetize commercial products, the orchestration plan with assetize orchestration item must be associated with the commercial product, not a technical product.

  

  Note

  An assetizable product cannot be a child of non-assetizable product.

See Orchestration Item Associations to Fulfillment Request Lines and Order Items

• Propagate Attributes from Fulfillment Requests: You can propagate the attributes from fulfillment request lines to their source order items. When you create the item implementation for the organization, you can then create an orchestration item to propagate the attributes for specific orchestration plans. For information on how to propagate attributes from fulfillment requests to order items, see Propagating Attributes from Fulfillment Requests to Order ItemsPropagate Attributes from Fulfillment Requests to Order Items (Back-Propagation).

• Send data to an integration procedure in OmniStudio: An auto task using the XOMTaskAutotaskIntegrationProcedure implementation sends information about an order to an integration procedure that you've already created. See Default Auto Task to Support Integration Procedures