Book Image

Mastering Apex Programming

By : Paul Battisson
5 (1)
Book Image

Mastering Apex Programming

5 (1)
By: Paul Battisson

Overview of this book

As applications built on the Salesforce platform are now a key part of many organizations, developers are shifting focus to Apex, Salesforce’s proprietary programming language. As a Salesforce developer, it is important to understand the range of tools at your disposal, how and when to use them, and best practices for working with Apex. Mastering Apex Programming will help you explore the advanced features of Apex programming and guide you in delivering robust solutions that scale. This book starts by taking you through common Apex mistakes, debugging, exception handling, and testing. You'll then discover different asynchronous Apex programming options and develop custom Apex REST web services. The book shows you how to define and utilize Batch Apex, Queueable Apex, and Scheduled Apex using common scenarios before teaching you how to define, publish, and consume platform events and RESTful endpoints with Apex. Finally, you'll learn how to profile and improve the performance of your Apex application, including architecture trade-offs. With code examples used to facilitate discussion throughout, by the end of the book, you'll have developed the skills needed to build robust and scalable applications in Apex.
Table of Contents (21 chapters)
1
Section 1 – Triggers, Testing, and Security
8
Section 2 – Asynchronous Apex and Apex REST
15
Section 3 – Apex Performance

Defining a schedulable Apex class

We define an Apex class that can be scheduled by implementing the Schedulable interface. Similar to our Queueable interface, it provides a single method, execute, which we must implement. We can see this in the following code:

public class SchedulableExample implements Schedulable {
   public void execute(SchedulableContext SC) {
      //Do something
   }
}

From the preceding code, we see that within the execute method, it is best practice to make a call to another class containing the logic we wish to run, rather than explicitly declaring the logic within the execute method itself. This primarily helps to ensure that you reuse code as much as possible and manage your separation of concerns, but this also makes the processing code easier to test by allowing you to test separately from the scheduled execution setup.

It is also important to recognize that our SchedulableExample class...