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

Calling future methods

As noted in the previous section, our future method is simply a static method, meaning we can call the method in the same way we would call any static method. For example, imagine our method was defined as follows:

public class FutureClass {
	@future
	public static void myFutureMethod() {
		//Method code
	}
}

Then, to invoke this method we would simply execute the following line of code within our code to call the function:

FutureClass.myFutureMethod();

We can call future methods from almost any Apex code we are executing with only a small number of exceptions. You cannot chain future methods together, so the following code would compile but would throw an exception when futureB() was invoked:

@future
public static void futureA() {
	//Code for futureA method
}
@future
public static void futureB() {
    //Execute some other code
    futureA(); //this would compile, but fail at runtime,    &...