In the Salesforce Communications Cloud data model, an active service is represented by an Asset record (the commercial view) and its underlying technical components and attributes are stored in Inventory Item records (the technical view). When an orchestration plan needs to know the existing configuration of a service it is modifying, the standard and correct practice is to retrieve this information from the associated Inventory Items. These objects serve as the technical source of truth for provisioned services within Salesforce, holding the specific attribute values (like the current service plan) that orchestration processes act upon.

A. The Change Order captures the delta or the new state; it doesn't typically store both old and new values on the commercial product itself.

C. Creating custom objects is not a best practice, as the standard data model with Assets and Inventory Items is designed specifically for this purpose.

D. A callout to an external system introduces unnecessary dependency and latency. The Salesforce inventory should be the system of record for this information during orchestration.

Salesforce Communications Cloud Developer Guide, "The Industries Data Model". This document outlines the relationship between Assets (what the customer bought) and Inventory Items (the technical details of what was provisioned), establishing Inventory Items as the source for technical attributes.

Salesforce Help, Industries Order Management, "Decomposition for MACD Orders". The documentation explains that decomposition logic uses the existing asset's state, which is derived from the technical inventory, to determine the necessary fulfillment actions.