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

Log levels

Now that we have a simple way of replicating the issue that can speed up our debugging, the next step for us is to ensure we have the correct level of logging. Salesforce debug logs have a limit of 20MB, which is a large amount of data for a purely text-based output and can end up with you viewing what amounts to a lot of noise about the transaction. Setting up our log levels correctly is going to help us immensely in weeding out the issue without too much additional data to scroll and read through.

We can set the granularity of our debug logs to a series of different levels across a number of categories. The categories and a brief description of what information they contain is provided in the following table:

Table 2.1 – Debug log categories

For each category, we can also define a log level from one of the following options:

  • NONE
  • ERROR
  • WARN
  • INFO
  • DEBUG
  • FINE
  • FINER
  • FINEST

This can give us over 100...