Task and Event

As per salesforce definition:

An event is a calendar event scheduled for a specific day and time.

Examples of events are:

1)      Meetings
2)      Scheduled Conference Calls

A task is an activity not scheduled for an exact day and time. You can specify a due date for a task or there may not be a particular time or date that the tasks or activities need to be completed by.

Examples of tasks are:

- A list of phone calls you need to make.
-  An email that needs to be sent. 

Question Dumps

1. In a custom application, you can include only a landing page.

A. True

B. False

2. Which of the following statements are true about custom objects? (select all that apply)

A. Salesforce provides a set of custom objects that you can use to store data

B. After you create a custom object, you need to add the user interface

C. Custom objects come with an infrastructure include reporting, auditing, and access control.

D. When you create a custom object, you get a direct access to the database.

E. Custom objects are reportable and searchable.

3. Which of the following statements is true about custom tabs?

A. A custom tab is a user interface component you create to display custom object data or other web content   embedded in the application

B. There are two types of custom tabs

C. Custom object tabs display any external web-based application or web page in a user interface tab.

D. Web tabs display the data of your custom object in a user interface tab.

4. Identify the correct statements about dependent picklists. (Select all that apply)

A. Standard picklists can be controlling fields but not dependent fields.

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

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

D. A custom multi-select picklist can be set as the controlling field for a dependent field.

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

5. When a customizing a page layout, you can change the filed locations, page setting customizations, and related list customizations.

A. True

B. False

6. Which of the following statements are true about a lookup relationship? (Select all that apply)

A. A maximum of 2 relationships is allowed per object

B. A lookup relationship can span to multiple layers.

C. A parent record is required for each child.

D. A lookup field is not a required field.

E. Access to parent determines access to children.

7. Custom formula fields are smart custom fields that can be used to build business-specific calculations using simple wizards and Excel-like formulas.

A. True

B. False

8. Which of these statements are true for cross-object formula fields? (Select all that apply)

A. You can reference cross-object formulas in roll-up summary fields.

B. You cannot reference merge fields for objects related to activities

C. You can use cross-object formula fields to reference record owner merge fields for any object.

D. The limit for cross-object formulas is 10 unique relationships per object across all formulas and rules

9. Which statements about roll-up summary formulas are correct? (Select all that apply)

A. They calculate values from a set of related records.

B. They are read/write formula fields

C. They can be created to display a value on a master record based on the values of records in a detail record.

D. They can be added for all lookup relationships.

10. If all error conditions are false, the corresponding error message is displayed and the save is aborted.

A. True

B. False

11. A change set can be used to deploy metadata only between ___Related_______ orgs

[Change Set ---A change set is a means by which one organization can send customizations to another organization. For example, you could create a new object in a sandbox organization and send it to your production organization using a change set. Change sets can only contain modifications you can make through the Setup menu; therefore, you can't use a change set to upload a list of contact records. In other words, change sets contain metadata, not data.

When you want to send customizations from your current organization to another organization, you create an outbound change set. Once you send the change set, the receiving organization sees it as an inbound change set.

Sending a change set between two organizations requires a deployment connection. Change sets can only be sent between organizations that are affiliated with a production organization—for example, a production organization and a sandbox, or twosandboxes created from the same organization.

]

12. What happens if one component of a change set fails to deploy?

A. The entire change set fails to deploy.

B. The entire change set gets deployed.

C. Except the failed component, all other components of change sets get deployed.

D. The deployment time increases.

13. Change sets can be used to move data and metadata from one organization to another.

A. True

B. False

Tab Settings

Tab settings specify whether a tab appears in the All Tabs page or is visible in its associated app. Tab settings labels in permission sets differ from the labels in profiles.

Enabled Settings in Permission Sets	Enabled Setting in Profiles	Description
Available	Default Off	The tab is available on the All Tabs page. Individual users can customize their display to make the tab visible in any app.
Available andVisible	Default On	The tab is available on the All Tabs page and appears in the visible tabs for its associated app. Individual users can customize their display to hide the tab or make it visible in other apps.
None	Tab Hidden	The tab isn’t available on the All Tabs page or visible in any apps.

Approval Process

An approval process includes the following elements:

• A name and description to distinguish it from other approval processes.
• Entry criteria if you only want records with certain attributes to be included.
• A designated user who can approve requests.
• Settings to specify who, if anyone, can change a record once it has been submitted for approval.
• Any number of steps that determine the sequence of actions to take when a record matches the criteria. Each step can have up to 40 actions, 10 of each type: email alerts, field updates, tasks, and outbound messages.
• Up to 40 additional actions that occur when a record is initially submitted.
• Up to 40 additional actions that occur when a record is approved.
• Up to 40 additional actions that occur when a record is rejected.
• Up to 40 additional actions that occur when a record is recalled.

For sending approval through email the following settings needs to be enabled .

Go to Setup--> Create ---> Workflow Approvals --->Settings and enable as shown below

Here one important things that should be kept in mind is that the User who approves on a certain object should have the correct permissions to do so. This can be done using Permission Set

Workflow Use case

Cross object Processes :

Set Default Opportunity Name

The opportunity naming convention for some companies is Account Name: Opportunity Name. To automate the default name of each opportunity in your organization, create the following workflow rule.

Object	Opportunity
Description	Enforce opportunity naming convention.
Evaluation Criteria	Evaluate the rule when a record is: created, and every time it’s edited.
Rule Criteria (Filter)	Run this rule if the following criteria are met: NOT(CONTAINS( Name, Account.Name ))
Immediate Actions	Field Update: Set opportunity name to the following formula: Account.Name & ": " & Name
Time-Dependent Actions	None.

Set Target Resolution Date for Cases

This example illustrates how to automatically set a case resolution date based on the value of a field on the associated account. It uses a custom picklist field on accounts called Support Level, which has three values–Basic, Standard, and Premium–as well as a custom date field on cases called Target Resolution Date.

Use the following three workflow rule examples to automatically set the target resolution date of a case based on the support level for the related account.

Set Resolution Date for Basic Support

Object	Case
Description	Sets the case target resolution date for accounts that have basic support level to 30 days from today.
Evaluation Criteria	Evaluate the rule when a record is: created.
Rule Criteria (Filter)	Run this rule if the following formula evaluates to true: ISPICKVAL(Account.Support_Level__c , "Basic")
Immediate Actions	Field Update: Set the Target Resolution Date to Today() + 30
Time-Dependent Actions	None.

Set Resolution Date for Standard Support

Object	Case
Description	Sets the case target resolution date for accounts that have standard support level to 14 days from today.
Evaluation Criteria	Evaluate the rule when a record is: created.
Rule Criteria (Filter)	Run this rule if the following formula evaluates to true: ISPICKVAL(Account.Support_Level__c , "Standard")
Immediate Actions	Field Update: Set the Target Resolution Date to Today() + 14
Time-Dependent Actions	None.

Set Resolution Date for Premium Support

Object	Case
Description	Sets the case target resolution date for accounts that have premium support level to 5 days from today.
Evaluation Criteria	Evaluate the rule when a record is: created.
Rule Criteria (Filter)	Run this rule if the following formula evaluates to true: ISPICKVAL(Account.Support_Level__c , "Premium")
Immediate Actions	Field Update: Set the Target Resolution Date to Today() + 5
Time-Dependent Actions	None.

Campaigns

A campaign is an outbound marketing project that you want to plan, manage, and track within Salesforce. It can be a direct mail program, seminar, print advertisement, email, or other type of marketing initiative. You can organize campaigns into hierarchies for easy analysis of related marketing tactics.

To manage campaigns, users must have the Marketing User check-box selected on their personal information page, the appropriate user permissions, and sharing access to the campaign.

With Campaigns - 

• Target and market to existing Leads and Contacts
• Generate new leads
• Track response rates on a Campaign
• Track Lead conversion rates on a Campaign
• Attribute Opportunities to a Campaign
• Calculate ROI

Campaign  Mechanics - 

• Create a Campaign
• Determine your Campaign member status
• Target Leads and Contacts
• Launch
• Measure 

OwnerID

                The OwnerID is the UserID of the person who owns the record in SFDC.  Without getting too nuts&bolts, when you look at a record through the UI you see the "Name" of the person who owns the record, but the value in the Owner field is actually the UserID.  Behind the scenes SFDC basically does a VLOOKUP against the User Object and displays the Name associated with OwnerID.  That's why when you export the raw data from SFDC you don't get the Owner Name, just their ID.  

For example the User ID starts with a 005, 00580000003I2xx, but the Owner ID starts with 00G, 00G80000001QW2m.

00G means the owner is a queue, not a user.