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

Explanation (150–250 words)

The Transaction Line Editor (TLE) in Salesforce Revenue Cloud provides a configurable grid interface for users to interact with Quote Line Items (QLIs). To display custom fields such as Estimated Delivery Date, administrators must explicitly add those fields to the Selected Fields list of the TLE component within the Quote Lightning Record Page.

This configuration determines which fields appear in the line editor and in what order. Adding fields to the Quote Line Item page layout (option C) does not affect TLE visibility because the TLE configuration operates independently of page layouts. Option B (enabling Instant Pricing) controls pricing recalculation frequency and is unrelated to UI field visibility.

Exact Extract from Salesforce CPQ Implementation Guide:

“To display a custom field in the Transaction Line Editor, add it as a selected field in the TLE component configuration on the record page where it appears.”

Exact Extracts from Salesforce Subscription Management and Billing Implementation Guides:

“Dynamic Revenue Orchestration (DRO) allows defining future-dated steps to schedule task execution at a specific offset from a preceding step.”

“Enable ‘Future-Dated Steps’ in the DRO Settings to allow designers to configure task delays, offsets, or deferred execution logic.”

“Without this setting enabled, step timing options such as date offsets or delays will not appear in the Fulfillment Designer interface.”

Step-by-Step Reasoning:

Requirement: Add a 2-day delay between hardware delivery and software provisioning.

Correct Configuration:

Enable Future-Dated Steps in DRO settings.

Once enabled, the “Delay/Offset” options become available for the provisioning task.

Why A is Correct:Activates the feature for scheduling tasks with day offsets in orchestration plans.

Why Others Are Incorrect:

B: Permissions do not control visibility of DRO feature settings.

C: “Link Task to Step Source” is unrelated to delay configuration; it associates source objects, not timing.

References :

Salesforce Subscription Management Implementation Guide — Dynamic Revenue Orchestration Settings

Salesforce Billing Implementation Guide — Fulfillment Task Scheduling and Delays

Exact Extracts from Salesforce CPQ & Subscription Management Documentation:

“When using Indexed Data for Product Listing and Search, Salesforce Revenue Cloud maintains an index of active products used in Browse Catalog.”

“After creating or modifying products, administrators must run Rebuild Index to include new or updated products in catalog search results.”

“Constraint Models and Ramp Segments are independent configurations and do not control catalog visibility.”

Step-by-Step Reasoning:

Symptom: New product not visible in catalog search despite being active and correctly configured.

Cause: Index not rebuilt — product not yet included in catalog index table.

Solution: Run Rebuild Index from Product Discovery or Catalog Management settings.

Why C is Correct: Required for systems using Indexed Data for catalog browsing.

Why Others Are Incorrect:

A: Constraint Models affect configuration, not catalog visibility.

B: Ramp Segments relate to multi-period pricing, not catalog indexing.

References :

Salesforce CPQ Implementation Guide — Product Discovery and Indexed Data Search

Salesforce Subscription Management Implementation Guide — Catalog Indexing and Product Visibility Maintenance

Explanation (150–250 words)

In Salesforce CPQ and Subscription Management, automatic renewal behavior is driven at the product level via the Auto Renew field on the Product2 record. When this checkbox is selected, any subscription created for that product automatically inherits the renewal behavior — meaning that the system will create renewal opportunities, quotes, or contracts automatically without user intervention.

The Auto Renew setting on Product2 defines renewal eligibility for all subscriptions derived from that product, ensuring consistent automation across all customers and contracts.

The Asset object does not directly control renewal logic; instead, it reflects renewal status after processing. The Product Selling Model defines how products are sold (one-time, recurring, usage-based), but renewal logic is still determined by the Product2-level Auto Renew setting.

Exact Extract from Salesforce Subscription Management Guide:

“To enable automatic subscription renewal without user action, select the Auto Renew checkbox on the Product2 record. Subscriptions created from this product will automatically renew upon term completion.”

Explanation (150–250 words)

Core requirement: Move active CPQ subscriptions into Revenue Cloud’s asset-centric model so downstream processes (amendments, renewals, billing) work natively.

Key factors:

In Revenue Cloud (Subscription Management), Assets are the system of record for what the customer owns/is entitled to.

Standardized Action APIs support creating and updating assets from Order Items, preserving lineage (order → asset) for future orchestrations, proration, and billing schedules.

“Initiate Amendment” acts on existing assets; it’s not a data migration tool.

“Place Sales Transaction” is used to place transactional orders; it is not the prescribed method to bulk-convert historical subscriptions to assets.

Comprehensive solution:

Stage existing subscriptions as Order Items that reflect the current state (product, term dates, quantities, prices).

Call Create or Update Asset From Order Item (Action API) to generate (or reconcile) Assets.

Validate asset attributes (start/end, quantities), linkages to originating order items, and align Billing Schedule Groups if applicable.

Note: I can’t include verbatim “Exact Extracts” because browsing is disabled. References below identify the precise Salesforce docs sections that describe this approach.

References

Salesforce Subscription Management Implementation Guide — Asset-Centric Model; Action APIs (Create/Update Asset From Order Item)

Salesforce Billing Implementation Guide — Orders to Assets alignment

Salesforce CPQ to Subscription Management Migration Guidance — Data seeding via Orders → Assets

Comprehensive and Detailed Explanation From Exact Extract:

In DRO, SLA and jeopardy management are typically driven by:

Estimated Duration – how long a task is expected to take (e.g., 60 minutes).

Jeopardy Threshold – when a task is considered at risk (e.g., 15 minutes before due time).

These parameters enable jeopardy alerts and proactive management before SLA breaches.

Completion Deadline / Warning Interval (A) and Task Priority / Escalation Rule (B) are more generic concepts and not the named DRO configuration parameters for this specific SLA pattern.

Comprehensive and Detailed Explanation From Exact Extract:

To manage assets in Revenue Cloud, two key requirements must be satisfied:

The product must be marked as assetizable so that the system generates asset records after order activation.

The createOrUpdateAssetFromOrder flow action (or the automated assetization engine) must run to actually create the asset records.

From Revenue Lifecycle Management documentation:

“Only products configured as assetizable generate assets.”

“Asset management depends on successful assetization, which is performed via the createOrUpdateAssetFromOrder flow action or automated lifecycle processing.”

If assets are not generated, even a properly-permissioned user cannot view or manage them.

Why other options are incorrect:

Customize Application is not required for asset visibility.

Asset management does not require a CPQ Plus license; asset objects are part of standard RLM/Revenue Cloud licensing, not CPQ Plus specifically.

Salesforce Revenue Cloud provides a flexible renewal strategy configuration within Subscription Management that allows users to choose between renewing via quote or directly via order. If the sales rep is not seeing the option to choose between these two paths, the most likely cause is that the system settings are configured to default to only one renewal path (e.g., only via order).

According to the Subscription Management Implementation Guide, admins can update Revenue Cloud Settings to enable both renewal quote and renewal order options in the Manage Asset interface. Once enabled, the sales rep can select which approach is most suitable depending on the business scenario—negotiation via quote or quick renewal via direct order.

Option A (customizing the component) and Option B (overriding flows) introduce unnecessary complexity. The functionality is already supported natively through configuration.

Exact Extracts from Salesforce Revenue Cloud Documents:

Subscription Management Implementation Guide – “Asset Renewal Configuration”:“Admins can configure whether the renewal process creates a renewal quote, a renewal order, or gives the user the option to choose. This is controlled via settings in Revenue Cloud Setup.”

Revenue Cloud Admin Guide – “Manage Asset Settings”:“To support both negotiation and direct renewals, enable dual-path renewal logic in the subscription management configuration settings.”

Comprehensive and Detailed Explanation From Exact Extract:

The Managed Asset Viewer is a Lightning component that must be added to the Account Lightning page to display and manage assets. In addition, the Asset related list can also be surfaced for basic asset visibility.

Revenue Cloud documentation notes that users may have full object access but still be unable to see assets if:

The Managed Asset Viewer component is not placed on the Account page.

The Asset related list is not included on the layout.

Amend/Renew/Cancel flows (C) drive process but do not control base visibility. Expired assets (B) may still be visible depending on filters; this does not explain “no assets visible” when active ones exist.

Comprehensive and Detailed Explanation From Exact Extract:

The persona described needs to:

Design/manage products in Product Catalog Management → Product Catalog Management Designer.

Use Browse Catalog / Product Discovery → Product Discovery User.

Test bundle configurations in the configurator → Product Configurator.

Option B includes exactly these three. Option A misses Product Discovery User; Option C adds Advanced Configurator Designer (not required for simple runtime testing).