Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Learning Apex Programming
  • Table Of Contents Toc
Learning Apex Programming

Learning Apex Programming

By : Matthew Kaufman, Wicherski
2.8 (6)
Buy this Book
close
close
Learning Apex Programming

Learning Apex Programming

2.8 (6)
By: Matthew Kaufman, Wicherski
Buy this Book

Overview of this book

If you are a developer who has some object-oriented programming experience, Learning Apex Programming is the perfect book for you. This book is most appropriate for developers who wish to gain an understanding of the Force.com platform and how to use Apex to create business applications.
Table of Contents (11 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. Apex Assumptions and Comparisons
Icon
1. Apex Assumptions and Comparisons
Icon
Before you start
Icon
A gift to our readers
Icon
Safety first
Icon
The Force.com IDE
Icon
Getting comfortable with Eclipse
Icon
Linking Eclipse to the Salesforce1 Platform
Icon
Under the hood
Icon
Data and metadata
Icon
Writing code
Icon
Summary
2
2. Apex Limits
Icon
2. Apex Limits
Icon
Exceptions prove the rule
Icon
Embracing an exception
Icon
An exception to end all exceptions
Icon
Obeying the speed limit
Icon
More limits
Icon
Edition limits
Icon
API limits
Icon
E-mail limits
Icon
Time and relative limits in space
Icon
You want me to process how many records?
Icon
How many times and how many things
Icon
Techniques to avoid query limits
Icon
These aren't the queries you're looking for
Icon
Visualforce limits
Icon
Summary
3
3. More and Later
Icon
3. More and Later
Icon
Chain reactions
Icon
Where we're going, we don't need roads
Icon
I fought the law and won
Icon
Please sir, I want some more
Icon
Combining forces
Icon
Bigger, better, and batchier
Icon
Dyna batch
Icon
Building skynet
Icon
Master control
Icon
Summary
4
4. Triggers and Classes
Icon
4. Triggers and Classes
Icon
A brief history of triggers
Icon
Trigger happy
Icon
Pulling the trigger
Icon
Inside the mind of a trigger
Icon
Class is in session
Icon
Staying classy
Icon
Put your hands together
Icon
Behind the scenes
Icon
The Pablo Picasso of Apex
Icon
Summary
5
5. Visualforce Development with Apex
chevron up
Icon
5. Visualforce Development with Apex
Icon
s-con, what?
Icon
Your own personal Force.com
Icon
Tag, you're it!
Icon
Taking control
Icon
Extending control
Icon
More internal goodies
Icon
Static cling
Icon
Dynamic pages
Icon
Visualforce components
Icon
Your component library
Icon
Controlling components
Icon
Summary
6
6. Exposing Force.com to the World
Icon
6. Exposing Force.com to the World
Icon
Three ways to skin a cat
Icon
JavaScript buttons jubilee
Icon
For your consideration
Icon
My turn!
Icon
Summary
7
7. Use Case – Integration with Google Calendar
Icon
7. Use Case – Integration with Google Calendar
Icon
Gimme an O!
Icon
Googol
Icon
Forget me not
Icon
I'm late, very, very late!
Icon
O, Auth me mighty Google!
Icon
Summary
8
8. Creating a Property Management Application
Icon
8. Creating a Property Management Application
Icon
Why
Icon
What
Icon
Who
Icon
How
Icon
When and Where
Icon
A custom model
Icon
Paying your dues
Icon
Mine, all mine
Icon
Ain't no mountain
Icon
Upgrade to the app status
Icon
Summary
9
9. Test Coverage
Icon
9. Test Coverage
Icon
@isTest
Icon
Always on my mind
Icon
Get tested
Icon
Fruits of our labour
Icon
The ultimate goal
Icon
Summary
10
Index
Icon
Index

Your component library

Although we don't spend much time writing comments in our code in this book, it's definitely a best practice to do so. This is especially true for Visualforce components because they are designed for reusability. If you and your colleagues don't want to reinvent the wheel, then you need to provide descriptive information about your components. Fortunately, there's a built-in Description attribute in components just for this purpose. You can access this Description attribute on the metadata of the component. In case you don't remember from Chapter 1, Apex Assumptions and Comparisons, the metadata for a file is accessed in the IDE via the Metadata tab at the bottom of the editor, as shown in the following screenshot:

Once you've provided a useful description for all of your components, you and your fellow developers can browse through the list of components from inside the Force.com GUI, as follows:

  1. Click on the Setup link at the top of the Force.com GUI.

  2. Navigate to Developer...

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Learning Apex Programming
End of Chapter 5
Next Chapter
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon