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

Debugging using the Apex Replay Debugger

The Apex Replay Debugger is a tool that allows a developer to replay a set of code that has been run to debug it at particular breakpoints. You can gain a deeper insight into the code as it runs and can inspect any variables for their values within VS Code. The Replay Debugger allows you to have up to five breakpoints within your code, so it has to be used with this in mind.

To use the Replay Debugger, perform the following steps:

  1. Open your org and ensure that your user has no debug logs turned on for your user.
  2. Once you have done this, return to your VS Code project and apply a set of checkpoints to your code. This is done by clicking on the gutter of the file (this is the area to the left of the line numbers).
  3. A red dot will appear signifying a breakpoint has been created, as is shown for the singleton instance we discussed previously, and shown in the following screenshot. Note that there is a difference in terminology...