Book Image

Salesforce Platform Enterprise Architecture - Fourth Edition

By : Andrew Fawcett
Book Image

Salesforce Platform Enterprise Architecture - Fourth Edition

By: Andrew Fawcett

Overview of this book

Salesforce makes architecting enterprise grade applications easy and secure – but you'll need guidance to leverage its full capabilities and deliver top-notch products for your customers. This fourth edition brings practical guidance to the table, taking you on a journey through building and shipping enterprise-grade apps. This guide will teach you advanced application architectural design patterns such as separation of concerns, unit testing, and dependency injection. You'll also get to grips with Apex and fflib, create scalable services with Java, Node.js, and other languages using Salesforce Functions and Heroku, and find new ways to test Lightning UIs. These key topics, alongside a new chapter on exploring asynchronous processing features, are unique to this edition. You'll also benefit from an extensive case study based on how the Salesforce Platform delivers solutions. By the end of this Salesforce book, whether you are looking to publish the next amazing application on AppExchange or build packaged applications for your organization, you will be prepared with the latest innovations on the platform.
Table of Contents (23 chapters)
1
Part I: Key Concepts for Application Development
6
Part II: Backend Logic Patterns
11
Part III: Developing the Frontend
14
Part IV: Extending, Scaling, and Testing an Application
21
Other Books You May Enjoy
22
Index

Object and field level security

Ensuring that object and field level security configuration is respected in your custom UIs is a key part of your responsibility to provide your customers with a secure solution. The standard UIs do this automatically for you, but it requires further consideration for custom UIs. In this section, we will explore how to do this for both LWC and Visualforce pages. Lightning Aura Components has more limited support for it.

The following custom UIs illustrate how object and field level security are applied (or not) depending on the binding approach and/or components used. This will help you understand when you need to add additional code or just rely on the standard components.

In the use case used in the next two sections, two users are used; one has full access, and the other has been given the following permissions via their profile:

  • Read-only access to the Status__c field
  • No access at all to the FastestLapBy__c field
...