Salesforce Revenue-Cloud-Consultant-Accredited-Professional - Salesforce Revenue Cloud Consultant Accredited Professional (AP-223)

Cross-object formula fields are useful for accessing data from relatedobjects, but they also have some drawbacks and risks, especially when used excessively in a revenue cloud project. Some of the risks are:

They can easily exceed limits if not carefully designed and tested. Cross-object formula fields count against the total number of fields allowed per object, and they also consume more resources than regular fields. If the formula is too complex or references too many objects, it can cause performance issues, errors, or failures. For example, a formula can only reference up to 10 unique relationships, and a record can only trigger up to 16 levels of cross-object formula updates. 12

Formula field data is not always available during CPQ quote calculation. CPQ quote calculation is a process that evaluates the pricing, discounts, taxes, and other factors of a quote. During this process, some cross-object formula fields may not have the latest data or may not be accessible at all, depending on the order of execution and the timing of the updates. This can lead to inaccurate orinconsistent results, or even prevent the quote from being calculated. 3

They are computationally expensive. Cross-object formula fields require more processing power and time than regular fields, as they need to query and calculate data from multiple objects and relationships. This can affect the overall performance and responsiveness of the revenue cloud project, especially when thereare many cross-object formula fields involved. Additionally, cross-object formula fields can trigger cascading updates and validations, which can further increase the computational load and complexity. 4

For a Revenue Cloud project where aproduct's taxability depends on a custom field that holds industry information, the appropriate solution is touse automation to set the Tax Rule based on the value of the custom field. This approach allows for dynamic application of tax rules to productsbased on industry-specific requirements, ensuring that the correct tax treatment is applied during the quoting and invoicing processes. Automation could involve using Process Builder, Flow, or Apex to update the tax rule assignments on products or quote lines based on the specified industry criteria. This ensures that products are taxed correctly according to the industry-specific regulations captured in the custom field.

These are three features that are not natively supported by Salesforce Revenue Cloud, but can be added by using an AppExchange Solution.

Contract Redlining: This is the process of comparing and editing different versions of a contract document,usually with track changes and comments. This can help to negotiate and finalize the terms and conditions of a contract with customers or partners. 1

Electronic Signature: This is the digital equivalent of a handwritten signature, which can be used to sign and validate a contract document electronically. This can help to speed up the contract approval process and reduce paper usage. 2

Attachments: This is the ability to add additional files or documents to a contract document, such as supporting evidence, product specifications, or legal disclosures. This can help to provide more information and clarity to the contract parties. 3

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.

Determiningwhether 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.

References

Test New Releases in a Sandbox Unit | Salesforce Trailhead

Salesforce Introduces Revenue Cloud to Help Businesses Accelerate …

Salesforce CPQ (Configure, Price, Quote) allows admins to automate price calculations and update quote line fields1. In the context of Universal Containers, they have three product families and want to view the net totals of these families at the quote level1. The current solutioninvolves creating three separate price rules that use summary variables to add the net total for quote lines that belong to a particular product family1. However, from a performance standpoint, it would be more efficient to use a single price rule with three price actions12. This isbecause price rules can inject a static value, field value, or summary variable into a quote or quote line field1. Therefore, having a single price rule with multiple price actions can streamline the process and improve performance12. References: 12

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 thatthe 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.

The three design examples that will negatively impact the scale and performance of the Revenue Cloud implementation are:

A. Multiple automation types (trigger/workflows,flows) on a single object: Having multiple automation types on a single object can lead to complex and inefficient processes. This can slow down the system and negatively impact the performance and scalability of the Revenue Cloud implementation1.

B. External API calls within the pricing sequence: Making external API calls within the pricing sequence can introduce latency and potential points of failure. This can slowdown the pricing process and negatively impact the performance and scalability of the Revenue Cloud implementation1.

C. Extensive use of quote line custom fields: Using a large number of custom fields can increase the complexity and size of the data model. This can slow down queries and negatively impact the performance and scalability of the Revenue Cloud implementation1.

The reasons for establishing a governance structure as part of your Revenue Cloud project include:

B. To establish a communicationplan between the implementation team, the customer, and the work is coordinated between them: This is essential to ensure clear and ongoing communication throughout the project, aligning all stakeholders towards common goals and facilitating timelyresolution of issues.

D. To get agreement on the roles and responsibilities of the implementation team and customer: Defining roles and responsibilities helps in setting clear expectations, distributing tasks, and accountability which are critical for theorganized progression of the project.

E. To ensure the implementation team is aligned with the customer on assigned work: Alignment on the assigned work ensures that both the implementation team and the customer have a mutual understanding of project objectives, deliverables, and expectations, leading to a smoother project flow and reducing the likelihood of misunderstandings and reworks.

These aspects are derived from the standard practices and objectives in implementing complex IT projects like SalesforceRevenue Cloud, where coordination, clear communication, and defined responsibilities are fundamental for success.

In Salesforce CPQ, a bundle is a group of products that are known to be sold together. There are three types of bundles: static, configurable, and nested1. The bundle configuration is a significant part of CPQ, and it can make selling complex product offerings easier by providing sales reps with premade product bundles to choose from1. However, whether a customer needs a bundle configuration or not depends on their specific needs and preferences2. Therefore, it’s important to introduce the concept of bundle configuration as part of a CPQ project, but the decision to implement it should be left up to the customer2. References

Learn About Configuration in the Sales Process - Trailhead

Product Bundles in Salesforce CPQ - SkyPlanner