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

Understanding the different types of exceptions

Broadly speaking, I like to divide exceptions into three types: expected exceptions, unexpected exceptions, and unknown exceptions. Let's look at what is meant by each of these types.

Expected exceptions

Expected exceptions are ones that we anticipate occurring and want to handle appropriately. An example would be some validation logic in code or a required field for a process to occur. When developing the code, you are aware of these items and the exceptions that they will throw and will want to inform the user appropriately. If they press the Send Invoice button and there is no email address, they should be informed.

Unexpected exceptions

Your code has been working for a period of time without any hiccups, then suddenly someone changes the system and does not verify the impacts of the change.

At the time of writing this, I have just been dealing with a bug in a system relating to a code-based process that was originally...