Free Salesforce Revenue-Cloud-Consultant-Accredited-Professional Practice Exam with Questions & Answers | Set: 3

 In Salesforce Revenue Cloud, the evaluation event of a product rule specifies when the rule should be evaluated. The options are:

Load: The rule will be evaluated when the product bundle is opened.

Edit: The rule will be evaluated when the product bundle is edited.

Save: The rule will be evaluated upon Save.

Always: The rule will be evaluated during anyevent.

In the context of the question, the requirement is to hide the hardware firewall product option while configuring the bundle if the customer has purchased a hardware firewall in the past. This means that the rule needs to be evaluated when the product bundle is being edited, not just when it is loaded or saved. Therefore, the correct answer is “Load and Edit”.

References

Salesforce CPQ Product Rules:General Considerations

Decide When Rules Evaluate Unit | Salesforce Trailhead

Product Rules - Salesforce

An invoice scheduler is a feature of Salesforce Revenue Cloud that allows you to automatethe 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 userstory, 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 donot 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 theimpact 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]

The three common CPQ design mistakes to avoid while implementing CPQ for your customer are:

A. Using price book entries to handle attribute based variationsinstead of lookup price rules: Price book entries are not designed to handle attribute-based variations. Instead, lookup price rules should be used. These rules allow you to adjust pricing based on specific product attributes, providing more flexibility and accuracy1.

C. Creating process builders and flows to pass data between fields instead of using twin field mapping: Process builders and flows can be complex and difficult to maintain. Instead, twin field mapping should be used. This feature allows you to map fields between objects, ensuring data consistency and reducing the need for custom code1.

D. Writing customizations for product selection or validation instead of using option constraints, product rules, and bundles: Customizations can be time-consuming and costly to implement and maintain. Instead, Salesforce CPQ provides built-in features like option constraints, product rules, and bundles that can handle product selection and validation. These features are designed to enforce business rules and ensure that only valid product combinations are selected1.

In Salesforce CPQ, when amending legacy contracts, encountering the 'attempt to de-reference a null object' error often points to issues with the underlying data structure of the migrated contracts and subscriptions. This error typically occurs when required fields are not present or are incorrectly populated, leading to null references in the system's code. It's essential to ensure thatall necessary fields on legacy contracts and subscriptions are correctly filled in to support amendments in Salesforce CPQ. This might involve reviewing and correcting the data migration process to ensure that all required fields are accurately populated and that the data integrity is maintained​​.