Book Image

Hands-On Low-Code Application Development with Salesforce

By : Enrico Murru
Book Image

Hands-On Low-Code Application Development with Salesforce

By: Enrico Murru

Overview of this book

Low-code platforms allow users to focus on business logic to create solutions without getting trapped in programming complexities. Thanks to its powerful features for designing, developing, and deploying apps without having to hand-code, Salesforce is at the forefront of the low-code development revolution. This book will guide you in building creative applications for solving your business problems using the declarative framework provided by Salesforce. You’ll start by learning how to design your business data model with custom objects, fields, formulas, and validation rules, all secured by the Salesforce security model. You’ll then explore tools such as Workflow, Process Builder, Lightning Flow, and Actions that will help you to automate your business processes with ease. This book also shows you how to use Lightning App Builder to build personalized UIs for your Salesforce applications, explains the value of creating community pages for your organization, and teaches you how to customize them with Experience Builder. Finally, you'll work with the sandbox model, deploy your solutions, and deliver an effective release management strategy. By the end of this Salesforce book, you’ll be ready to customize Salesforce CRM to meet your business requirements by creating unique solutions without writing a single line of code.
Table of Contents (28 chapters)
1
Section 1: What Is Salesforce?
3
Section 2: Data Modeling
9
Section 3: Automation Tools
15
Section 4: Composing the User Interface
19
Section 5: Data Management
22
Section 6: Ready to Release?
25
Section 7: Before We Say Goodbye

Sharing rules

So far, all users have the same sharing configuration on records:

  • They can read and edit all records from objects with a Public Read/Write OWD.

  • They can read (but not edit) all records from objects with a Public Read-only OWD.

  • They are not allowed to access any records they don't own if those records are under a Private OWD.

If the user owns a record that is Private or Public read-only, they'll always be allowed to read and edit the record and, if access is granted through hierarchies, the user's managers will be allowed to access the record as well.

What if we need to spread up sharing to users that are outside an owner's hierarchy?

To give an example, let's say we have a case with an OWD set to Private; this means that all cases created by any service agent won't be accessible to the sales SVP, as service agent roles lay on a parallel branch of the sales SVP hierarchy, which is lead by the service SVP (in Figure...