Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Mastering Apex Programming
  • Toc
  • feedback
Mastering Apex Programming

Mastering Apex Programming

By : Paul Battisson
4.9 (12)
close
Mastering Apex Programming

Mastering Apex Programming

4.9 (12)
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)
close
1
Section 1 – Triggers, Testing, and Security
8
Section 2 – Asynchronous Apex and Apex REST
15
Section 3 – Apex Performance

The Salesforce order of execution

Let's start this chapter by covering the Salesforce save order of execution. It is my opinion that the save order of execution should be one of the first things taught to every administrator or developer working on the platform. This ensures they are aware of the implications of actions they make when building automation through either clicks or code. Why is this?

Think of the save order of execution as being similar to a nuclear reactor. Nuclear reactors use fission to create energy, a process which involves firing a neutron at an isotope, with it then splitting and releasing some energy and other small isotopes. The reason I'm using this as a comparison is that it is a stable system that is designed to function in a certain way. As long as the process is controlled, we get the right amount of fission, and energy is released. If it goes wrong, though, too much energy is released, and this can cause a meltdown. If it is completely uncontrolled...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete