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 future methods

A future method must be defined as a static method with a void return type, as shown in the following code snippet. We annotate the method with the @future annotation to inform the compiler that this method should be called and placed onto the asynchronous processing queue:

@future
public static void myFutureMethod() {
	//method for execution
}

The method must be static so that it can be called and executed without the need for any state to be stored for it to execute.

We can also specify callout = true in the @future annotation to declare that the method can make callouts. By default, a standalone @future annotation is the same as @future(callout = false), barring our future method from making callouts to external systems. A method defined to make callouts would then be declared as follows:

@future(callout = true)
public static void myFutureCalloutMethod() {
	//make an API request
}

Our future method may have parameters in its definition, however...