During Scoping the customer indicated that they neededcustomization to salesforce CPQDue to a process in a legacy system what is the first stepin ensuring the requirement isAccounted for in Scoping?
Correct Answer: A
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. References: Salesforce Introduces Revenue Cloud, Starting with CPQ: 8 Most Common Reasons for Customization
What does INVEST stand for in the INVEST criteria when defining user stories?
Correct Answer: D
INVEST is an acronym that stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable12. It is a set of criteria used to assess the quality of a user story in Agile methodologies12. Here's what each term means: * Independent: The user story should be self-contained, in a way that there is no inherent dependency on another user story12. * Negotiable: User stories, up until they are part of an iteration, can always be changed and rewritten12. * Valuable: A user story must deliver value to the end user12. * Estimable: You must always be able to estimate the size of a user story12. * Small: User stories should not be so big as to become impossible to plan/task/prioritize with a certain level of certainty12. * Testable: The user story or its related description must provide the necessary information to make test development possible12. References: 12
A revenue cloud customer has posted a cash payment that was created on account A by mistake.what are the stepsto apply this to the correct invoice on account B?
Correct Answer: B
In Salesforce Revenue Cloud, if a cash payment has been posted to the wrong account by mistake, the recommended steps to correct this are as follows: Allocate the Payment: If the payment has been allocated, the first step is to allocate the payment. This means assigning the payment to the specific invoice it was intended for. Create a Refund: Once the payment has been allocated, the next step is to create a refund. This will effectively reverse the payment that was made in error. Create a New Payment for Account B: After the refund has been created, a new payment can be made for the correct account (Account B in this case). This payment should be allocated to the correct invoice on Account B: It's important to note that these steps ensure that the payment records are accurate and reflect the correct allocation of funds. This is crucial for accurate financial reporting and for maintaining the integrity ofthe account's payment history. References: Use Payments to Correct Errors on Posted Refunds - Salesforce Make a Payment on an Invoice - Salesforce Paymentsand Credits - Salesforce
You are implementing the Design Document for a large Enterprise Revenue Cloudprojecthaving multiple lookup price rules supporting a complex pricing requirement in the Buildphase. During construction the customer discovers additional logic and external datastores that need to be incorporated in order to achieve the correct pricing in a particular setof use cases. You estimate the lookup price rules will need to be modified, additional ruleswill need to be created and API development will beneeded. As an Implementationconsultant what is the appropriate course of action that should take in this predicament?
Correct Answer: C
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. References: * 1: Salesforce Revenue Cloud Implementation Guide, page 17 * 2: Lookup Price Rule query considerations with Salesforce CPQ 3
Some of the users at universal containers have faced long processing times during quote document generation. What can be done to reduce the processing times for document generation?
Correct Answer: C
Reducing processing times during quote document generation in Salesforce CPQ can be achieved through various optimizations. One effective method is using compressed image formats for image files included in the quote document. This reduces the file size of the images, leading to faster loading and processing times when generating quote documents. While the specific reference to this practice is not directly available in the provided Salesforce Revenue Cloud documents, it is a widely recognized optimization technique in document generation processes to enhance performance and reduce loading times.