According to the Salesforce Revenue Cloud CPQ documentation, users need to have the Create,

Read, Edit, and Delete permissions on the Quote object in order to create and manage quotes. If

users do not have the proper access to the Quote object, they will encounter errors when trying to

create quotes, even if the quotes are set as primary by default. This is because the primary quote

field is a lookup field that

the Quote object, and users need to have access to the

referenced object in order to populate the lookup field. Therefore, the most likely cause of the issue

is that the users did not have the proper access to the Quote object in the production environment,

and this was not detected in the sandbox environment because the users had different permissions

or profiles there. Reference:

https://help.salesforce.com/s/articleView?id=000316738&language=en_US&type=1

https://help.salesforce.com/s/articleView?id=000381216&language=no&type=1

In Salesforce CPQ, ensuring that users have the proper access to the Quote object is crucial for the

smooth creation and management of quotes. The issue reported by users in the production

environment, where errors occurred upon trying to create quotes for the first time, likely stemmed

from insufficient permissions on the Quote object. In CPQ, setting a new quote as "primary" at the

time of creation is a common practice to streamline the quoting process. However, if users lack the

necessary permissions on the Quote object, they would encounter errors when attempting to create

or modify quotes. It's important to note that in Salesforce CPQ, orders must be created from a

primary quote, and once an order is created from a primary quote, the quote cannot be edited  . This

indicates that the underlying issue is related to access permissions on the Quote object, rather than

post-installation scripts, access to the Opportunity Product object, or access to the Quote Line object.

When a Revenue Cloud customer needs to add more items from another order to a posted invoice

without using invoice batches, the recommended approach is to "Cancel and Rebill" the invoice. This

process involves rolling the invoice back to its state before the most recent billing cycle, allowing

corrections or additions to be made to the invoice record. This action is applicable to both draft and

posted invoices and is designed to address errors or changes needed on the invoice, such as adding

new order items  . This method ensures that all necessary adjustments are made while maintaining

the integrity of the invoice's audit trail and data.

According to the Salesforce Revenue Cloud Implementation Guide, any changes to the design

document during the build phase should be communicated to the project manager, who will assess

the impact of the changes on the project scope, timeline, and budget. The project manager will then

decide whether to accept, reject, or defer the changes, and update the project plan accordingly. This

is the best practice to ensure that the project is delivered on time, on budget, and with the expected

quality and functionality.

Implementing the lookup price rules immediately without consulting the project manager or the

solution architect could result in errors, inconsistencies, or conflicts with the existing design or other

components of the solution. It could also cause delays or rework if the changes are not aligned with

the customer’s expectations or requirements. Therefore, option B and option E are not appropriate.

Consulting with the solution architect first could help to expedite the updates to the design

document, but it would still require the approval of the project manager and the customer before

implementing the changes. Therefore, option D is not sufficient.

Communication to the customer that ongoing adjustments can be made as long as we are in the

build phase could create confusion or unrealistic expectations about the project scope and timeline.

It could also undermine the credibility and authority of the project manager and the solution

architect, who are responsible for managing the project and ensuring the quality of the solution.

Therefore, option A is not advisable.

Reference:

1: Salesforce Revenue Cloud Implementation Guide, page 17

2: Lookup Price Rule query considerations with Salesforce CPQ 3

A Revenue Cloud consultant needs to understand the client’s business, their products or services,

and their sales process before they can effectively scope a Revenue Cloud project.

A . A sample proposal the client provides to their customers: This document can give the consultant

insights into the client’s current sales process, pricing strategies, and customer interactions1.

B . Brochures that provide detail to the products and services the client offers: These materials can

help the consultant understand the client’s product offerings, their unique selling points, and how

they position themselves in the market1.

D . An approval matrix documentation that describes the approvals needed before a quote is sent to

the customer: This document can help the consultant understand the client’s internal approval

processes, which is crucial for configuring the approval workflows in Revenue Cloud2.

C . The latest release notes found at help.salesforce.com>salesforce CPQ patch notes: While these

notes are important for staying updated on the latest features and bug fixes in Salesforce CPQ, they

may not directly help the consultant understand the client’s specific project requirements3.

E . The client’s income statements and balance sheet: While these financial documents can provide

valuable insights into the client’s financial health and performance, they may not directly contribute

to understanding the client’s Revenue Cloud project requirements1.

Reference: Salesforce Revenue Cloud documents1, Salesforce Approval Processes2, Salesforce CPQ

Patch Notes3.

The steps that an implementation team should take to integrate Revenue Cloud with another system

are:

B . Complete a source to target mapping of the fields that will integrate between systems: This step

involves defining how data fields in Revenue Cloud correspond to data fields in the external system.

It is crucial for ensuring accurate data flow and integration functionality between the systems.

D . Design an architecture view of how data integrates and flows between systems: This involves

creating a detailed architectural blueprint that outlines how data will be transferred and managed

between Revenue Cloud and the external system. It helps in identifying potential integration

challenges and ensuring that the integration supports the business processes effectively.

These steps are based on best practices in systems integration, focusing on data consistency and

integrity, along with a structured approach to designing integration flows.

When a customer indicates the need for customization to Salesforce CPQ due to a process in a legacy

system, the first step in ensuring the requirement is accounted for in scoping is to ask follow-up

questions to ensure the legacy process has a business justification. This is important because it helps

to understand the business needs and requirements better, and ensures that the customization will

add value to the business. It’s crucial to understand the ‘why’ behind the need for customization

before proceeding with it. This approach helps in avoiding unnecessary customizations and ensures

that the solution aligns with the business objectives. Reference: Salesforce Introduces Revenue

Cloud, Starting with CPQ: 8 Most Common Reasons for Customization

The benefits of having trained customer CPQ admins participate in the planning, design, and build

phases include:

A . Facilitates a more efficient test phase: Trained CPQ admins can leverage their understanding of

both the platform's capabilities and the company's specific requirements to craft more effective tests

and more quickly identify potential issues.

E . Customer is better equipped to scale and maintain functionality post-go-live: With deep

involvement in the project phases, CPQ admins gain a thorough understanding of the setup and

customization, which empowers them to manage, scale, and adapt the system as business needs

evolve without always relying on external support.

These benefits highlight the importance of involving knowledgeable internal team members in

significant project phases to ensure long-term success and operational efficiency.

An invoice scheduler is a feature of Salesforce Revenue Cloud that allows you to automate the

creation of invoices based on predefined criteria and schedules. An invoice scheduler uses an invoice

run to evaluate whether and when an order product gets invoiced. You can set up an invoice

scheduler to run daily, weekly, monthly, or once, and specify the target date and time, the invoice

date, and the invoice batches to include. You can also choose to automatically post the generated

invoices or review them in draft status before posting. An invoice scheduler is the best option to

fulfill the user story, as it can generate invoices in draft status the same day of every month without

requiring any manual intervention or custom code. 12

Triggers and apex are not the best option, as they require writing and maintaining custom code,

which can be complex and error-prone. They also do not provide the flexibility and control of an

invoice scheduler, as they can only check the bill now checkbox after the order status is changed to

“Activated”, which may not match the desired invoicing schedule or criteria. 3

Workflow rules are also not the best option, as they have similar limitations as triggers and apex.

They can only check the bill now checkbox after the order status is changed to “Activated”, and they

cannot specify the invoice date, time, or batches. Workflow rules also have some restrictions and

considerations, such as the number of actions per rule, the order of execution, and the impact on

performance. 4

Setting up a payment scheduler is not relevant to the user story, as it is a feature of Salesforce

Revenue Cloud that allows you to automate the collection of payments from customers based on

predefined criteria and schedules. A payment scheduler does not create invoices, but rather applies

payments to existing invoices or payment allocations. [5]

Reference:

1: Invoice Schedulers for Automating Invoice Creation - Salesforce

2: Invoice Scheduler | Salesforce Subscription Management | Salesforce Developers

3: Use Invoice Scheduler to Generate Invoices - Salesforce

4: Workflow Rules Considerations - Salesforce

[5]: Payment Schedulers for Automating Payment Collection - Salesforce

Enable Large Configurations on Specific Bundles: Instead of enabling large configurations globally for

all bundles, consider selectively enabling it only on the bundle parents where it is needed. By doing

so, you can avoid affecting smaller bundles that don’t require large configurations. This approach

allows you to optimize performance while still benefiting from large configurations where necessary.

Review CPQ and Billing Design Solutions: Take a closer look at your CPQ and billing design. Ensure

that your configuration models, pricing rules, and quote line editor settings are well-optimized.

Sometimes, design choices can impact performance. Consider consulting Salesforce documentation

and best practices to fine-tune your implementation.

Avoid Unnecessary Use of Large Configurations: While large configurations can handle complex

bundles, they may not be needed for smaller bundles with fewer products. Evaluate each bundle’s

complexity and enable large configurations only when necessary. Avoid using it indiscriminately

across all bundles.

Reference:

Salesforce Enable Large Configurations Documentation

Salesforce Trailhead: Understand Scalability

Salesforce Revenue Cloud Overview

Salesforce AppExchange offers a variety of solutions that can enhance the functionality of Salesforce

Revenue Cloud. Here are the reasons why you would need an AppExchange solution to support

generating a document in support of a Revenue Cloud project:

Watermarks (A): Watermarks can be used to mark documents as confidential or to denote the status

of the document (draft, approved, etc.). AppExchange solutions can provide this functionality, which

is not available out-of-the-box in Salesforce.

Electronic Signature ©: Electronic signatures are often required for contracts and other legal

documents. AppExchange solutions like DocuSign can integrate with Salesforce to provide this

functionality.

Contract Redlining (D): Contract redlining allows for tracking changes and comments during the

contract negotiation process. This is a specialized functionality that can be provided by AppExchange

solutions.

Reference

10 Benefits of Using Salesforce AppExchange Apps - Cloud Analogy

Revenue Cloud Collection Page - Salesforce

Extending Customer 360 with Salesforce AppExchange

What Is Salesforce AppExchange and How Can I Use It?