A customer wants to define default entitlement for data storage that they want to sell.What should they use to accomplish this?
Answer(s): A
In Salesforce Revenue Cloud, when a customer wants to define a default entitlement for a usage- based service (such as data storage), they should use a Product Usage Grant. This object is used to define:The default quantity or amount a customer is entitled toThe type of usage (e.g., data, API calls, minutes)Any limits or allowances that are bundled with a subscription or productProduct Usage Grants are tied to the commercial product and are part of the entitlement management model in Salesforce Subscription Management. They enable entitlement tracking and enforcement of usage limits.Product Usage Resource defines the type of resource being measured (e.g., "Data Storage").Rate Card Entries are used to define pricing for overage or tiered usage, not entitlements.Therefore, to specify the default amount included with a product, the correct object is Product Usage Grant.Exact Extracts from Salesforce Revenue Cloud Documents:Subscription Management Implementation Guide "Usage-Based Entitlements":"Use Product Usage Grants to define the included entitlements (e.g., 5GB of storage) that a customer receives with their subscription."Revenue Cloud Product Setup "Usage Grant vs. Usage Resource":"Product Usage Resource defines what is measured. Product Usage Grant defines how much is granted."
Salesforce Subscription Management Implementation GuideRevenue Cloud Usage-Based Product Configuration GuideSalesforce CPQ and Billing Object Reference
A company is implementing Revenue Cloud to automate its subscription renewals. A Revenue Cloud Consultant needs to configure the system to allow sales reps to initiate the renewal process for a customer's active assets directly from a record page.Which component must the consultant implement to provide this one-click renewal capability?
The most effective and supported way to enable one-click subscription renewals in Salesforce Revenue Cloud is to use a Screen Flow that calls the InitiateRenewal invocable action. This invocable action is provided as part of Salesforce Subscription Management and allows for the programmatic initiation of a renewal process on active assets.By embedding this flow as a Quick Action on a Contract, Subscription, or Account record page, sales reps can start the renewal process directly from the UI without manual data entry or navigation. This aligns with Salesforce best practices for declarative automation using Flow.Option B (Apex trigger) is not recommended, as renewals are typically initiated by user intent, not automatically based on dates.Option C (custom checkbox and Process Builder) is a workaround that lacks the flexibility, reliability, and maintainability of Flow + invocable action.Exact Extracts from Salesforce Revenue Cloud Documents:Subscription Management Implementation Guide "Renewals with Screen Flow":"Use the InitiateRenewal invocable action in Flow to allow users to initiate renewals from record pages."Revenue Lifecycle Automation Guide "Renewal Automation":"Expose the InitiateRenewal action via Flow as a quick action for guided user-initiated renewals."
Salesforce Subscription Management Implementation GuideSalesforce Revenue Lifecycle Automation GuideSalesforce Flow Developer Guide
For Lot-based or As-Is Renewals, how should a user trace an Asset's renewal price breakdown back to its original Net Unit Price?
Answer(s): C
In Salesforce Revenue Cloud, particularly when managing Lot-based or As-Is Renewals, the system tracks pricing and lifecycle changes using the Asset Action object. This object represents a single lifecycle event (e.g., purchase, renewal, upgrade) that occurred to an asset and captures:Net Unit Price at the time of actionAction type (e.g., renewal, cancellation)Source and target pricing metadataTo trace back the renewal price to the original net unit price, users should examine the Asset Action records associated with the asset. Each action contains detailed pricing information at the time the action was executed, enabling full auditability.Option A (Asset State Period) tracks state over time but doesn't store pricing breakdowns.Option B (Asset Action Source) is used to relate an asset action to its originating object (e.g., order or quote), but not to track pricing details.Exact Extracts from Salesforce Revenue Cloud Documents:Subscription Management Implementation Guide "Asset Actions and Renewals":"Asset Actions provide visibility into pricing and changes during renewals, upgrades, and other lifecycle events. The Net Unit Price is recorded in the Asset Action record."Asset Lifecycle Guide "Understanding Asset Actions":"Use Asset Action records to audit price changes over time, including renewal-specific pricing breakdowns."
Salesforce Subscription Management Implementation GuideSalesforce Revenue Lifecycle GuideAsset Lifecycle and Renewal Data Model Reference
Universal Containers (UC) recently acquired another company called Cloud Kicks (CK). UC uses Revenue Cloud to manage its Product-to-Cash business process. CK manages its process using a custom app with standard Salesforce objects like Asset, Quote, Order, etc. Both Salesforce orgs will be merged into a single org with different processes until a long-term solution is implemented. Sales leadership would like to clearly differentiate between the assets sold by UC and those sold by CK.How should this be achieved out of the box?
The standard way to identify whether an Asset is managed by Salesforce Revenue Cloud's Lifecycle Management engine is by using the HasLifecycleManagement field. This out-of-the-box field is a Boolean value on the Asset object that indicates whether the asset is tied to Revenue Lifecycle- managed records (e.g., originating from CPQ+ or Subscription Management flows).This field enables reporting, filtering, and business logic to segment Revenue Cloud-managed assets from assets generated through custom or legacy systems like CK's app. It is the most appropriate solution in this scenario as it requires no customization and is supported natively by Salesforce.Option B suggests creating a custom field, which is unnecessary since the platform already provides a system field for this purpose.Option C (Asset Action Source) refers to tracing asset actions to originating events, but it is not suitable for broad classification of asset origin or management type.Exact Extracts from Salesforce Revenue Cloud Documents:Subscription Management Implementation Guide "Asset Data Model":"The HasLifecycleManagement field flags whether an asset is lifecycle-managed by Revenue Cloud. This is useful in environments where assets come from multiple systems."Revenue Cloud Data Dictionary "Asset Object":"Use HasLifecycleManagement to distinguish system-managed assets from externally generated or legacy assets."
Salesforce Subscription Management Implementation GuideSalesforce Revenue Cloud Data DictionaryAsset Lifecycle Management Documentation
A Salesforce Developer is using Postman to retrieve a JSON response with Product2 IDs to develop a Lightning web component.Which query parameters are valid when using the Products List (POST) API to retrieve a list of products for the component?
When using the Products List (POST) API in Salesforce Revenue Cloud, developers can query and filter the list of available products using specific supported parameters. According to the Salesforce Product Catalog and Discovery API documentation, the valid and commonly used filters for the Products List API include:Product2 IDs: to retrieve specific products directly by their IDCatalog IDs: to filter products based on a specific product catalogCategory IDs: to filter products that belong to a particular category within a catalogThis allows developers to fetch only relevant products for a specific UI component or experience, such as in a Product Discovery component or a custom Lightning Web Component (LWC).Option B includes Pricebook IDs, which are not supported as filter parameters in the Products List API. Pricebooks are used in pricing context but are not valid query parameters for this API endpoint.Option C includes ProductClassification IDs, which are not supported directly in the POST filter payload of the Products List API.Exact Extracts from Salesforce Revenue Cloud Documents:Product Discovery API Developer Guide "Products List (POST)":"Use Catalog IDs, Category IDs, and Product2 IDs as input filters in the POST request to retrieve relevant product records for discovery or display."Revenue Cloud API Reference "Querying Product Records":"The Products List API supports filtering by catalog, category, and direct product identifiers.Pricebooks are not queryable through this API."
Salesforce Revenue Cloud Product Discovery API GuideProduct Catalog and Discovery Developer DocumentationSalesforce CPQ API Reference (Fall '23 and Spring '24 Releases)
Post your Comments and Discuss Salesforce Rev-Con-201 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Rev-Con-201 content, but please register or login to continue.