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

Safety in numbers


Now we have a basic trigger under our belt. Let's look at what might happen if we fire that trigger with one record. If this trigger fires with a single contact record, it will update every case related to that contact whenever the contact's phone number is changed. However, triggers rarely run with only one record, and because of this, our example trigger has a number of flaws. If the trigger executes with two records, this trigger will only modify those cases where the contact ID matches the first contact record. However, the Salesforce1 platform does not guarantee that our triggers will fire with a single record. In fact, with this platform, it is quite clear that triggers will execute with at least 1 but no more than 200 records at a time. Because of this, we have to write our triggers to handle up to 200 records at a time. It may seem odd that 1 trigger would have to handle 200 records being updated at the same time, but remember that any code that inserts a list of...