Salesforce Rev-Con-201 - Salesforce Certified Revenue Cloud Consultant

For migrating an install base to Revenue Cloud with focus on Amendments and Renewals, the correct objects are Asset, Asset Action, Asset State Period, and Asset Action Source. These objects form the foundation of Revenue Cloud's Asset Lifecycle Management, which is essential for tracking customer subscriptions and enabling amendment and renewal processes.

The Asset object represents products or services that customers have purchased and own. It contains critical information about what the customer has, including quantity, pricing, and contract relationships. The Asset Action object tracks all changes made to assets throughout their lifecycle, including new purchases, amendments, renewals, and cancellations. Each asset action creates a historical record of modifications.

Asset State Period is crucial as it represents time spans when an asset has the same quantity, amount, and monthly recurring revenue (MRR). According to the Revenue Cloud Developer Guide, "An asset has as many asset state periods as there are changes to it (asset actions) during its lifecycle." This object is essential for accurate revenue recognition and reporting.

Asset Action Source links back to the originating transaction (Quote or Order) that created or modified the asset, maintaining data lineage. This traceability is vital for amendments and renewals, as Revenue Cloud needs to understand the complete history of each asset.

Option B includes legacy CPQ objects (Subscription, Subscribed Asset) that are not part of Revenue Cloud's asset management model. Option C focuses on transactional objects rather than asset tracking. The Asset Lifecycle Management objects in Option A are specifically designed to support the amendment and renewal workflows that are critical to the customer's business requirements.

The correct approach to refresh prices for existing assets without service disruption is to amend the original asset, leave the original quantity unchanged, and use the reprice functionality. This method ensures continuity while updating pricing terms.

When amending an asset in Revenue Cloud, the amendment flow allows sales reps to create an amendment quote reflecting the desired changes. The amendment quote inherits the asset's current configuration while allowing price adjustments. By leaving the quantity unchanged but rephricing the quote, the system applies the new pricing without requiring the customer to purchase additional units or experience a service gap.

After repricing the amendment quote with the updated prices, the sales rep creates and activates an order from the quote. Upon order activation, the system processes the amendment by creating new Asset Actions that update the asset's financial terms while maintaining the customer's existing subscription. This approach preserves service continuity because the asset never goes inactive; it simply gets updated with the new pricing terms effective from the amendment start date.

Option A (negate quantity and re-add) would create unnecessary complexity and could cause momentary service gaps as the original quantity goes to zero before re-adding. This approach is inefficient for simple price updates. Option C (changing end date and re-adding) similarly creates duplication and potential service disruption. The reprice amendment approach, per the Amendment Creation process documented in Revenue Cloud, is the streamlined method that updates pricing while maintaining uninterrupted customer service.

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.”

Exact Extracts from Salesforce Revenue Cloud (CPQ & Billing Implementation Guides):

“During quote-to-contract conversion, the selection options presented in the discount popup are derived from the Contract Item Price object’s Discount Type picklist field.”

“Administrators can remove or rename values from the Discount Type picklist to customize which discount options appear to users during the conversion process.”

“The screen flow and LWC components rely on metadata values; modifying these underlying picklist entries changes the available options in the UI.”

Step-by-Step Reasoning:

Requirement: Remove “None” option from the discount-selection popup.

Configuration Location: The options come from Contract Item Price → Discount Type picklist.

Solution: Remove the “None” picklist value in object metadata setup.

Why B is Correct:Declaratively removes the undesired value from the popup.

Why Others Are Incorrect:

A: The “Create Contract From Quote” flow references existing metadata and does not define picklist values.

C: LWC modification is not required for removing a metadata-driven value.

References :

Salesforce Billing Implementation Guide — Quote-to-Contract Conversion and Discount Mapping

Salesforce CPQ Implementation Guide — Contract Item Price Configuration