Most Recent Salesforce Revenue-Cloud-Consultant-Accredited-Professional Exam Dumps

In Salesforce CPQ, if a custom field is an input to product prices and you want a change in this field to trigger a recalculation, you should add this field to the calculating fields field set.This is because Salesforce CPQ's Advanced Quote Calculator determines quote and quote line prices in response to user or automated actions1. Therefore, adding the 'partner type' field to the calculating fields field set will ensure that setting the partner type on the quote triggers a new calculation.Reference

The CPQ Quote Calculation Sequence - Salesforce

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 that all 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.

To design a multi-leveled approval matrix for controlling discounts on quotes, Universal Containers should consider the following:

Identify backup approvers in case the primary approver is out of the office. This will ensure that the approval process is not delayed or stalled due to the unavailability of the primary approver. Backup approvers can be assigned using the Delegated Approver feature in Salesforce, which allows users to delegate their approval authority to another user for a specific period of time.1

Define the discount threshold or limit allowed for the sales reps. This will help to enforce the pricing policies and prevent excessive or unauthorized discounts. The discount threshold or limit can be defined using the Approval Thresholds feature in Salesforce CPQ, which allows setting up different approval rules based on the discount percentage, amount, or margin.2

Document the discount approval levels for each approver. This will help to clarify the roles and responsibilities of each approver and the criteria for approving or rejecting a quote. The discount approval levels can be documented using the Approval Processes feature in Salesforce, which allows creating a sequence of steps and actions that an approval request must go through.3

Approval Thresholds

Approval Processes

Delegated Approver

Having the customer's Executive sponsors participate in the kickoff of a Revenue Cloud implementation is crucial for several reasons:

A . To endorse project plan and timelines of the transformation efforts: Executive sponsorship is essential for endorsing and supporting the project plan and timelines. Their backing ensures that the project aligns with broader organizational goals and gets the necessary resources and attention.

C . To assure project objectives are being met: Executive sponsors help in assuring that the project objectives align with the business's strategic goals. Their presence in the kickoff meeting reinforces the importance of these objectives and ensures they are clearly communicated and understood by all stakeholders.

E . To provide finality in escalations paths: Involving executive sponsors in the kickoff provides a clear escalation path for addressing issues that might arise during the implementation. This setup helps in resolving conflicts or challenges swiftly, ensuring the project stays on track.

Executive involvement from the beginning underscores the strategic importance of the project, facilitates alignment on expectations and resources, and establishes a clear governance structure.

User stories are short, simple descriptions of a feature or functionality from the perspective of the end user or customer. User stories are used to capture the requirements and value proposition of a product or service in an agile framework. User stories should follow some best practices to ensure clarity, consistency, and alignment with the business goals and user needs.12

Some of the key steps when documenting user stories are:

Know which business process the requirement supports to categorize the user story. This helps to prioritize and organize the user stories based on the business value and impact they deliver. It also helps to avoid duplication and inconsistency among user stories.3

Identify the actor or personas in this user story. This helps to define the user role, needs, goals, and motivations that drive the user story. It also helps to create empathy and understanding for the user and their context.4

Identify the acceptance criteria or result for satisfying the user story. This helps to specify the expected outcome, behavior, or functionality that the user story should deliver. It also helps to define the scope, quality, and testability of the user story.5

Designing the solution while the business process is being defined is not a key step when documenting user stories. This can lead to premature or biased decisions that may not address the real user problem or value proposition. User stories should focus on the what and why, not the how. The solution design should be done after the user stories are validated and prioritized, and in collaboration with the development team and other stakeholders.6

Documenting user acceptance test scripts for the user story is not a key step when documenting user stories. This can be done later, after the user stories are refined and detailed, and before the development and testing phases. User acceptance test scripts are used to verify that the user story meets the acceptance criteria and the user expectations. [7]

1: User Stories | Examples and Template | Atlassian

2: How to Write Perfect User Stories (With Templates): A Step-By-Step Guide | airfocus

3: 10 Tips for Writing Good User Stories - Roman Pichler

4: The Anatomy of a User Story | Scrum Alliance | Includes Template

5: Best Practices to Succeed with User Stories - DZone

6: UX documentation: Guide, best practices, template