We're on Agentforce Revenue Management (ARM). We have a requirement to periodically check whether a Renewal Quote (auto-generated ahead of a contract's end date) still matches the current state of the customer's Assets — since amendments or cancellations can happen after the renewal quote is created but before it's finalized. Our objective is to refresh the renewal quote for any changes in the Contract after the renewal quote is created.
We're trying to understand the correct data model traversal for this in ARM, given the objects involved:
- Contract — the source contract being renewed
- Asset — related to the Contract
- AssetContractRelationship — junction object between Asset and Contract
- AssetAction — the transaction log capturing lifecycle events (amend, renew, cancel) on an Asset
Questions for the community:
- What is the standard/recommended relationship path from a Quote (or Contract) to determine which Assets are currently associated with it — direct Asset.ContractId, or through AssetContractRelationship? When does ARM use one versus the other?
- Is AssetAction intended to be queried directly to detect "has this Asset changed since a given date," or is that considered an anti-pattern (i.e., should current state be read only from Asset's own fields, with AssetAction treated purely as historical/audit data)?
- Is there a standard/OOTB field or relationship that ties a Quote or its Quote Line Items back to the Asset(s) it's renewing, or is Contract the only reliable join point?
- Are there known data model diagrams or official Salesforce documentation that cover this specific Quote/Contract/Asset/AssetContractRelationship/AssetAction relationship set for ARM specifically (as opposed to CPQ Classic)?
Any pointers to official documentation, Trailhead modules, or real implementation experience would be appreciated.
Escribir una respuesta...
0/9000