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

Using custom exception types

Salesforce allows developers to extend the standard Apex Exception class to build custom exceptions that can provide bespoke errors and messages. To create a custom exception class, simply extend the standard Exception class as follows:

public with sharing class CustomisedException extends Exception {
    
}

We can throw an exception of our new type using the throw keyword:

throw new CustomisedException('This is the exception message`);

Custom exception classes allow us a greater degree of control over the messages that are displayed within exceptions that are thrown and can also allow us to take action in throwing an exception when one would not typically be thrown or be thrown incorrectly.

Consider the following code, which is making a callout to a RESTful web service and receives a status code back that is not a 200 OK code. Apex code will not error here (nor should it by default), however, we need to ensure that...