Book Image

Salesforce Sales Cloud – An Implementation Handbook

By : Townsend
Book Image

Salesforce Sales Cloud – An Implementation Handbook

By: Townsend

Overview of this book

Salesforce Sales Cloud is a system rich in functionality, addressing many sales business challenges such as sales productivity, forecast visibility, and sales enablement. However, unlocking the full value of the system and getting maximum returns pose a challenge, especially if you’re new to the technology. This implementation handbook goes beyond mere configuration to ensure a successful implementation journey. From laying the groundwork for your project to engaging stakeholders with sales-specific business insights, this book equips you with the knowledge you need to plan and execute. As you progress, you’ll learn how to design a robust data model to support the sales and lead generation process, followed by crafting an intuitive user experience to drive productivity. You’ll then explore crucial post-building aspects such as testing, training, and releasing functionality. Finally, you’ll discover how the solutions’ capability can be expanded by adding and integrating other tools to address typical sales use cases. By the end of this book, you’ll have grasped how to leverage Sales Cloud to solve sales challenges and have gained the confidence to design and implement solutions successfully with the help of real-world use cases.
Table of Contents (20 chapters)
1
Part 1:Building the Fundamentals
7
Part 2: Preparing to Release
13
Part 3: Beyond the Fundamentals

Testing low code versus pro code

One of the key benefits of the Salesforce platform is its declarative, low-code tools. The declarative approach makes some changes, such as adding fields, really simple and almost trivial. With this quick pace of change, it is easy to get swept along and forget that any testing is required. In this example, the field itself is only one element. It needs to be on the correct page layouts, be visible and editable by the right Users, and be checked to ensure that if it is a required field or has validation, existing processes do not break. These other elements can be easily overlooked but have significant security and integration implications. No system-enforced process requires declarative changes to be tested. However, as the capability of the low-code tools increases, as seen with the automation capability of Flows, there is a move to introduce testing options. Now, you have options to debug your Flows and for some types of Flows, you can also create...