Book Image

Salesforce Platform App Builder Certification Handbook

By : Siddhesh Kabe
Book Image

Salesforce Platform App Builder Certification Handbook

By: Siddhesh Kabe

Overview of this book

The Salesforce Certified Platform App Builder exam is for individuals who want to demonstrate their skills and knowledge in designing, building, and implementing custom applications using the declarative customization capabilities of Force.com. This book will build a strong foundation in Force.com to prepare you for the platform app builder certification exam. It will guide you through designing the interface while introducing the Lightning Process Builder. Next, we will implement business logic using various point and click features of Force.com. We will learn to manage data and create reports and dashboards. We will then learn to administer the force.com application by configuring the object-level, field-level, and record-level security. By the end of this book, you will be completely equipped to take the Platform App Builder certification exam.
Table of Contents (17 chapters)
Salesforce Platform App Builder Certification Handbook
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Preface
Index

Restricting data access


The most crucial part of any enterprise-level application (built on Salesforce or otherwise) is the control of data. The litmus test for the effectiveness of an enterprise-level application is the way in which we restrict unauthorized access to data.

The following diagram illustrates the record sharing in an organization:

The four records A, B, C, and D are evenly distributed between the reps and the Manager. Rep 1 should only see record A, Rep 2 should only see record B, and so on.

At the top of the chain, the Super Manager can see all the records under him.

Before we design the application, we first need to consider the stakeholders of the application:

  • Who will be using the application?

  • What will these users do?

  • Is the data sensitive or critical?

  • Who will be customizing the application?

  • Are there any global records that should not be edited by the users?

  • Which set of users will be editing which data?

These are some of the questions that need to be addressed before we understand...