FINE

DEBUG

WARNING

INFO

WARM

Database changes

http callouts

XML behind metadata configurations

Resources used by Apex

Failed WebMtoMlead submissions

Create a lookup relationship on both objects to a junction object called Job
Posting Applications.

Create a master-detail relationship in Job Postings custom object to the
Applications custom object.

Create a master-detail relationship in the Applications custom object to the
Job Postings custom object.

Create a lookup relationship in the Applications custom object to the Job
Postings custom object.

Executing methods as different users.

Executing methods for negative test scenarios.

Loading the standard Pricebook ID using a system method.

Loading test data in place of user input for Flows.

Better performance for custom Salesforce1 Mobile apps.

More centralized control via serverMside logic.

More pre-build component to replicate the Salesforce look and feel.

Better integration with Force.com sites.

public MyController(List<Object> objects){
accounts = (List<Account>)objects;
}

public MyController(List<Object> objects){
account = (Account) obj;

public MyController(){
account = new Account();
}

public MyController(ApexPages.StandardController
stdController) {
account = (Account) stdController.getRecord();
}

On Quote using Orders records.

On Opportunity using Opportunity Product records.

On Campaign using campaign member records.

On Account using Opportunity records.

On Account using Case records.

Developer Console

Force.com Migration Tool

Force.com IDE

Workbench

Create a formula field.

Create a required Visualforce component.

Create a required comments field.

Create a validation rule.

In a Custom Controller.

In a Standard Extension

In a Standard Controller

In a Controller Extension

Create a lookup relationship between the Candidate and Interview objects.

Create a roolMup summary field on the Candidate object that counts
Interview records.

Create a trigger on the Interview object that updates a field on the
Candidate object.

Create a masterMdetail relationship between the Candidate and Interview
objects.

If(o.account == a.id)

update contactList;

List <Contact> contacts = [SELECT Id, Salutation, FirstName, LastName,
Email FROM Contact WHERE AccountId =:a.Id];

System.debug(‘Amount of CPU time (in ms) used so far: ‘ +
Limits.getCpuTime());

Developer Console

Force.com MIgration tool

Force.com IDE

Workbench

Validation rules

Exception handling

Page layouts

Workflow alerts

Lookup filters

It terminates a line of code

It is often read aloud as “bang”

It cannot be used with Apex Triggers

It reverses the outcome of a Boolean statement

Standard picklists can be controlling fields but not dependent fields

The maximum number of values allowed in a controlling field is 400

Before defining a dependency, you should ensure that your picklist has at
least one value

A custom multiMselect picklist can be set as the controlling field for a
dependent field

If a field represents both a controlling field and a dependent field, it cannot
contain more than 300 values

By using the isCreatable() method.

By using the isInsertable() method.

By using the isAccess() method.

By using the isCreate() method.

As a List<String> with each value as an element in the list.

As a String with each value separated by a comma.

As a String with each value separated by a semicolon.

As a Set<String> with each value as an element in the set.

Custom button

Custom link

Apex trigger

Visualforce page

Command line

To generate a PDF document with application data.

To modify the page layout settings for a custom object.

To deploy components between two organizations

To create components for dashboards and layouts.

When developing web service client applications, use Developer Sandbox,
which is an exact replica of your Salesforce deployment, including all
customization and data.

New client applications should use the most recent version of the
Force.com WSDL file to fully exploit the benefits of richer features and
greater efficiency.

SOAP API is the most practical when processing data sets that contain
hundreds of thousands of records.

The Apex data loader runs on the SOAP API by default.

5

7

3

1

Model: What schema and data does salesforce uses to represent the
system completely.

View: How the schema and data is represented.

Controller: How the interface actions. Controllers are used to perform the
actions whenever users interact with visual force.

ANT Migration Tool

Workbench Metadata Retrieval

Developer Console

Salesforce UI Apex Test Evacution

ApexPages.StandardSetController controller = new
ApexPages.StandardSetController(Database.getQueryLocator(‘Sel
ect Id from Account Limit 1’));

ApexPages.StandardSetController controller = new
ApexPages.StandardSetController([SELECT Id FROM Account LIMIT
1]);

ApexPages.StandardController controller = new
ApexStandardController(Database.getQueryLocator(‘Select Id
from Account Limit 1’));

ApexPages.StandardController controller = new
ApexPages.StandardController([SELECT Id FROM Account LIMIT
1]);

Using the Set data structure to ensure distint records.

Using synchronous to callouts to call external systems.

Using @future methods to perform DML operations.

Using the Map data structure to hold query results by ID

Support specialized or complex business processes.

Support out of the box Salesforce functionality

Don't need to connect to or integrate with thirdMparty systems.

Provide highly customized user interfaces or customized clickMthrough
paths.

The invoices should have a lookup relationship to the Account.

The invoices should have a MasterMDetail relationship to the Account.

The Accounts should have a lookup relationship to the Invoice.

The Accounts should have a MasterMDetail relationship to the invoice.

Are usually faster and cheaper to build.

Generally require less maintenance.

Receive automatic upgrades when the tools are improved.

Aren’t subject to governor limits.

By using a rollMup formula field on the child record to include data from the
parent record.

By using merge field syntax to retrieve data from the parent record.

By adding a second standard controller to the page for the parent record.

By using SOQL on the Visualforce page to query for data from the parent
record.

No message is logged

Generic Exception

NullPointer Exception

List Exception

251

102

100

101

252

Determine if a datetime field has passed using the NOW function.

Return and display a field value another object using VLOOKUP function.

Generate a link using the HYPERLINK function to a specific record in a
legacy system.

Display the previous value for a field using the PRIORVALUE function.

Determine which of three different images to display using the IF function.

A crossMobject formula field on the Account object.

An Apex trigger on the Account object.

A Process Builder on the Account object.

A Workflow Rule on the Account object.

Query for test data using SeeAllData=true. Execute runallTests(). Verify
taht the results are correct.

Create data for testing. Call the method being tested. Verify that the result
are correct.

Query for test data using SeeAllData=true. Call the method being tested.
Verify taht the result are correct.

Create data for testing, Execute runAllTests().Verify that the result are
correct.

Debug Statement

Time

Namespace

Exception

C

B

D

A

IsTest(SeeAllData=false)

Id pricebookid = Test.getStandardPricebookId();

ListobjList = Test.loadData(Account.sObjectType, ‘myResource’);

Pricebook pb = new Pricebook();

By using ApexMessage.Message() to display an error message after the
number of DML statements is exceded.

By using Messaging.SendEmail() to continue the transaction and send an
alert to the user after the number of DML statements is exceded.

By using Pagereference.setRedirect() to redirect the user to a custom
Visualforce page before the number of DML statements is exceded.

By using Limits.getDMLRows() and then displaying an error message before
the number of DML statements is exceded.

A contact with empty values.

An empty List of Contacts.

A Contact initialized to null.

An error that no rows are found.

They requiere a deployment connection.

They can be used to transfer Contact records.

They can be used only between related organizations.

They use an all or none deployment model.

They can be used to deploy custom settings data.

Add the TestVisible attribute to the Apex class.

Add the SeeAllData attribute to the test methods.

Add the TestVisible attribute to the Apex methods.

Add the SeeAllData attribute to the test class.

Developer Sandbox

Partial Copy Sandbox

Unlimited Edition

Developer Edition

Third-party web service code.

JavaScript controller actions.

Third-party Javascript code.

Visualforce controller actions.

{ Setup.Url_Settings__c.Instance[Profile.Id].URL__c}

{ Setup.Url_Settings__c[$Profile.Id].URL__c}

{ Setup.Url_Settings__c.URL__c}

{ Setup.Url_Settings__c[Profile.Id].URL__c}

DEBUG

WARN

INFO

FINE

After update

Before update

After insert

Before insert

Using a <link> tag.

Using an <apex:includeScript> tag.

Using a <script> tag.

Using an <apex:define> tag.

Create a masterMdetail relationship to represent the oneMtoMmany model of
engines to parts.

Create a junction object to relate many engines to many parts through a
masterMdetail relationship.

Create a lookup relationship to represent how each part relates to the
parent engine object.

Create a junction object to relate many engines to many parts through a
lookup relationship.