Book Image

Mastering Application Development with Force.com

By : Kevin J. Poorman
Book Image

Mastering Application Development with Force.com

By: Kevin J. Poorman

Overview of this book

Force.com is an extremely powerful, scalable, and secure cloud platform, delivering a complete technology stack, ranging from databases and security to workflow and the user interface. With salesforce.com's Force.com cloud platform, you can build any business application and run it on your servers. The book will help you enhance your skillset and develop complex applications using Force.com. It gets you started with a quick refresher of Force.com's development tools and methodologies, and moves to an in-depth discussion of triggers, bulkification, DML order of operations, and trigger frameworks. Next, you will learn to use batchable and schedulable interfaces to process massive amounts of information asynchronously. You will also be introduced to Salesforce Lightning and cover components—including backend (apex) controllers, frontend (JavaScript) controllers, events, and attributes—in detail. Moving on, the book will focus on testing various apex components: what to test, when to write the tests, and—most importantly—how to test. Next, you will develop a changeset and use it to migrate your code from one org to another, and learn what other tools are out there for deploying metadata. You will also use command-line tools to authenticate and access the Force.com Rest sObject API and the Bulk sObject API; additionally, you will write a custom Rest endpoint, and learn how to structure a project so that multiple developers can work independently of each other without causing metadata conflicts. Finally, you will take an in-depth look at the overarching best practices for architecture (structure) and engineering (code) applications on the Force.com platform.
Table of Contents (16 chapters)
Mastering Application Development with Force.com
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Infinite cosmic power, itty bitty safety rope


As I said before, triggers on the Force.com platform are incredibly flexible. That flexibility comes at the cost of safety and structure. Aside from the basic syntax of a trigger header Trigger UpdateContactPhoneNumberOnCase on Contact (after update) {, there are no hard and fast rules we have to follow. This often leads to objects having multiple, long, or complex triggers. Among the many freedoms you have with triggers, you have the ability to create multiple triggers on the same object. For instance, you can have 2 or 200 triggers on the account object. As your org grows through the years, you can imagine the number of triggers on the same object rising, not declining. However, imagine a scenario where over the course of 5 years, your company has built five triggers on the account object and you're tasked with fixing a bug—which of the triggers do you look at? Hopefully, the filenames are helpful, but realistically, you're now sifting through...