Salesforce Certified Revenue Cloud Consultant Accredited Professional Practice Test - Questions Answers, Page 2

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]

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

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.

When encountering a Salesforce Sales Cloud implementation with multiple triggers, workflow, and flow processes applied to the Opportunity object, it is advisable to recommend consolidating these automations into a single type. This approach is recommended to optimize performance and maintainability, reducing complexity and potential conflicts between different automation types. Consolidating automations into one trigger, process builder, or flow ensures a more streamlined and efficient execution of business logic, contributing to better system performance and easier troubleshooting and maintenance.

Cross object formula fields are fields that reference data from related objects using lookup or master-detail relationships. They can be useful to display information from parent or child objects without creating custom code or workflows. However, using too many cross object formula fields in a Revenue Cloud project can pose some risks, such as:

Formula field data is not always available during CPQ quote calculation. This means that the formula fields may not reflect the latest values from the related objects when the quote is being generated or updated. This can cause inaccurate pricing, discounts, or taxes. To avoid this, it is recommended to use CPQ fields or custom fields instead of cross object formula fields for quote calculation.12

They are computationally expensive. This means that the formula fields require more processing power and time to evaluate and display the data from the related objects. This can affect the performance and responsiveness of the application, especially if there are multiple formula fields on the same object or page layout. To avoid this, it is recommended to limit the number and complexity of cross object formula fields, and use filters or conditions to reduce the number of records that need to be evaluated.34

They can easily exceed limits if not carefully designed and tested. This means that the formula fields can cause errors or warnings if they exceed the maximum length, number, or level of relationships allowed by Salesforce. For example, a formula field can only reference up to 10 unique relationships and span up to five levels of relationships. If these limits are exceeded, the formula field will not save or display correctly. To avoid this, it is recommended to review the formula field limits and best practices, and test the formula fields in different scenarios and environments.

1: Lookup Price Rule query considerations with Salesforce CPQ [7]

2: Salesforce CPQ Quote Calculation Stages [8]

3: What Is a Cross-Object Formula? - Salesforce [9]

4: Tips for Reducing Formula Size and Complexity - Salesforce [10]

5: Formula Field Limits - Salesforce [11]

Upon noticing an error on a posted invoice, the recommended corrective action is to use the 'Cancel and Rebill' feature. This process allows an admin to roll back the invoice to its state before the most recent billing cycle, enabling the correction of errors on the invoice record. This functionality is applicable to both draft and posted invoices, providing a way to address issues such as missing invoice lines or incorrect billing details. After canceling and rebilling, the admin can correct the order as needed and proceed to create and post a new invoice, ensuring the accuracy of billing records.

In Salesforce Revenue Cloud, when a new release is being deployed, it's important to test the implementation against the new release before it deploys to production. This can be achieved by:

Reviewing status.salesforce.com to determine refresh cutoff for the new release: Salesforce provides information about the refresh cutoff for the new release on status.salesforce.com. This allows you to know when the new release will be available in the sandbox for testing.

Determining whether your sandbox is on a preview or non-preview instance: Salesforce refreshes preview sandboxes a month before each major release. Regular, non-preview sandboxes are refreshed toward the end of the release cycle. Knowing whether your sandbox is on a preview or non-preview instance can help you plan your testing schedule accordingly.

It's worth noting that while Salesforce ensures that all sandboxes are upgraded, the timing of the upgrade can vary depending on whether the sandbox is on a preview or non-preview instance. Submitting a ticket to support when you want your sandbox updated is not a standard practice for preparing for a new release.

Reference

Test New Releases in a Sandbox Unit | Salesforce Trailhead

Salesforce Introduces Revenue Cloud to Help Businesses Accelerate ...