ADM301 Certification Topics

ADM301 Exam Outline Details
Contents
Software as a Service (SaaS) ................................................................................................................... 3 Ideas Overview:................................................................................................................................... 3 New Release Information ................................................................................................................... 6 Answers Overview: ............................................................................................................................. 7 CRM Content Overview: ..................................................................................................................... 8 Force.com (Platform as a Service) ........................................................................................................ 12 Force.com platform .......................................................................................................................... 12 The Cloud computing model ............................................................................................................. 12 Types of Applications suitable for Force.com ................................................................................... 13 Salesforce localization....................................................................................................................... 13 Application Essentials ........................................................................................................................... 15 Objects, Fields, Relationships ........................................................................................................... 15 Formula Overview: ............................................................................................................................ 17 Custom Buttons and Links ................................................................................................................ 18 Usage of Custom Buttons ................................................................................................................. 20 Button Overrides and Visualforce ..................................................................................................... 20 Security and Access ............................................................................................................................... 21 Sharing Model Overview:.................................................................................................................. 21 What are the salesforce.com audit levels? ....................................................................................... 23 Delegated Administration Overview:................................................................................................ 25 Delegating Administrative Duties ..................................................................................................... 25 Territory Management Overview: .................................................................................................... 25 Record Types versus Page Layouts ................................................................................................... 27 Implementing Business Processes ........................................................................................................ 29 Workflow rules.................................................................................................................................. 29 Approval Proces ................................................................................................................................ 31 In what order are automation rules and Apex triggers processed? ................................................. 34 Process Visualizer Overview ............................................................................................................. 34 Managing Data ...................................................................................................................................... 35 Data Loader Overview....................................................................................................................... 35 How can I identify the attachments in my Data Export? .................................................................. 35 How to Export attachments? ............................................................................................................ 36 Cees van der Sluis Winter12 1|Page

Salesforce.com Data Export Service ................................................................................................. 36 Data Definitions: ............................................................................................................................... 37 Dirty Data .......................................................................................................................................... 38 Retrieving Data ................................................................................................................................. 38 There are several ways to retrieve data out of Salesforce: .............................................................. 38 De-duplicating data........................................................................................................................... 38 Analytics & Reporting ........................................................................................................................... 41 Best Practices for Managing Storage Usage: .................................................................................... 41 Mass Delete: ..................................................................................................................................... 41 Adoption Dashboards ....................................................................................................................... 41 Force.com Code (Apex) ......................................................................................................................... 44 Apex Code Overview ......................................................................................................................... 44 When to use Apex ............................................................................................................................. 45 When not to use Apex (Use the Web Services API Instead) ............................................................. 45 Apex use cases .................................................................................................................................. 45 Dynamic Approval Routing leveraging Apex ..................................................................................... 45 How to access IDE Tools and Apps.................................................................................................... 46 Force.com Pages (Visualforce) .............................................................................................................. 47 Force.com Pages ............................................................................................................................... 47 Visualforce key features.................................................................................................................... 48 Visualforce Controllers...................................................................................................................... 48 Where Can Visualforce Pages Be Used? ........................................................................................... 49 Integrations ........................................................................................................................................... 50 Salesforce - Web Services API ........................................................................................................... 50 Web Controls & External Web App Integrations .............................................................................. 50 Increasing User Adoption.................................................................................................................. 51 Force.com Connect for Microsoft Office Overview ........................................................................ 52 Force.com Connect Offline Overview ............................................................................................... 53 Sandbox & Development as a Service .................................................................................................. 55 Development as a Service ................................................................................................................. 55 Force.com Sandbox ........................................................................................................................... 55 Create new Sandbox ......................................................................................................................... 56 Force.com Sandbox Setup Tips and Considerations ......................................................................... 57
Cees van der Sluis
Winter12
2|Page
Software as a Service (SaaS)

Ideas Overview:
Introduction Salesforce CRM Ideas is a community of users who post, vote for, and comment on ideas. Consider it an online suggestion box that includes discussions and popularity rankings for any subject. You can display a community to the following types of users: Internal Salesforce users only. Salesforce users can access all communities regardless of whether the community is internal-only or displayed in a portal. Customer Portal or partner portal users. Public users (requires setting up a Force.com Site). Salesforce CRM Ideas Setup To set up Salesforce CRM Ideas, complete the following steps: 1. Set up a Customer Portal. 2. Customize Salesforce CRM Ideas settings. 3. Create a community. 4. Define picklist values for the Categories and Status fields. 5. Set up Idea reports for your users. 6. Create validation rules that prevent offensive language from being used in the community. 7. Set up a Force.com site to display Salesforce CRM Ideas publicly. 8. Use the Ideas base theme to customize the look and feel of your Ideas user interface. Merging Ideas As more users contribute to a community, the number of duplicate ideas often increases. Duplicate ideas make it difficult to measure feedback because votes and comments are spread out over many similar ideas. The best way to resolve this issue is to merge duplicate ideas together so one idea becomes the master to one or more child ideas. Note the following about merging ideas: All votes belonging to child ideas are transferred to the master idea. If the same community member votes for two ideas that are eventually merged, only the vote for the master idea is kept; the vote for the child idea is discarded. Once you merge ideas they cannot be separated. Users can only vote for and add comments to a master idea. Child ideas become read-only. You cannot merge ideas in separate communities. Deleting a parent idea automatically deletes all child ideas. Child ideas cannot be deleted individually. The master idea does not inherit the status and category values of its child ideas. When an idea is merged and becomes a child idea, the child idea still appears on the Ideas Submitted page but not on any other pages in a community member's Recent Activity.
Cees van der Sluis
Winter12
3|Page

Assigning a Status to Ideas After an idea goes through your organization's review process, you can update the status of the idea so community members can keep track of its progress. Monitoring New Ideas and Comments As the Salesforce CRM Ideas administrator, you should regularly monitor new ideas and comments to make sure the content is appropriate for the community. Some tasks you should perform on a recurring basis include: Delete ideas or comments that contain spam or offensive language. If offensive language continues to be a problem, you can create a validation rule that prevents community members from using specific words when posting ideas and comments. Remove community members that post inappropriate content on a recurring basis. Post a comment to provide official information or additional detail that you want the community to know about. We recommend you identify yourself as a community expert when posting comments. The best way to monitor new postings is to regularly review the Recent Ideas and Comments tabs. Category, Ideas Categories are administrator-defined values that help organize ideas into logical sub-groups within a community. The View Category drop-down list on the Ideas tab allows users to filter ideas by category, and the Categories picklist on the Post Ideas page lets users add categories to their ideas. For example, if your ideas community has the focus Improvements to our clothing line, then you might set up categories such as Shirts, Jackets, and Slacks. Each organization has one common set of categories that can be added or removed from each community. An administrator defines separate categories for their ideas and answers communities. Comment Comments are plain text responses to posted ideas that enable discussions about the ideas. On the Ideas tab, the Comments subtab lists the comments that have most recently been submitted. On the detail page of an idea, comments are sorted in chronological order from oldest to newest. Community Communities help organize ideas and questions into logical groups with each community having its own focus and unique ideas and questions. Professional Edition organizations can have only one internal ideas community. All other editions can have up to 50 communities shared between ideas and answers. Community Application The Community application includes the ideas and answers features. The Community app is available in the Force.com app menu.
Cees van der Sluis
Winter12
4|Page

Community Expert A community expert is a member of the community who speaks credibly and authoritatively on behalf of your organization. When a community expert posts a comment or idea, a unique icon () displays next to his or her name so other community members can easily identify credible information within the community. The Salesforce administrator can designate as many community experts as necessary. Demote If you dislike an idea, you can click demote to subtract 10 points from its overall score and decrease the idea's overall popularity ranking. You cannot demote the same idea more than once, and after you demote an idea you cannot promote it. An idea can have negative overall points if more users demote the idea than promote it. Half-life The half-life setting determines how quickly old ideas drop in ranking on the Popular Ideas subtab, to make room for ideas with more recent votes. A shorter half-life moves older ideas down the page faster than a longer half-life. This setting affects all communities in your organization. Idea Ideas are suggestions posted by the members of an ideas community. For example, if the focus of a particular community is Ideas for car features, an appropriate idea for that community might have the title Insulated cup holders that keep your beverage hot or cold. Or, if the focus of a particular community is Ideas for our company's employee benefits, an appropriate idea for that community might have the title On-site day care. Point A point is a unit of measurement that represents the popularity of an idea. Each vote for an idea is worth ten points (promote adds 10 points and demote removes 10 points). An idea's total number of points displays to the left of the idea. Popular Ideas On the Popular Ideas subtab, ideas are sorted by an internal calculation that reflects the age of an idea's positive votes. Regardless of an idea's static total number of points, ideas with newer positive votes display higher on the page than ideas with older positive votes. This allows you to browse ideas that have most recently gained popularity, with less precedence given to long-established ideas that were positively voted on in the past. For more information, see the terms Point and Halflife. Portal If your organization has a Customer Portal or Partner Portal, you can add the Ideas tab to either or both portals so that portal users can participate in their own Salesforce CRM Ideas communities. The
Cees van der Sluis
Winter12
5|Page

Community list at the top of the Ideas tab lists all the available communities, and each community contains its own unique group of ideas. Promote If you agree with or like an idea, click promote to add 10 points to the idea. You cannot promote the same idea more than once and you cannot promote an idea that you have already demoted. Salesforce automatically adds your promote vote to any idea you post. Recent Activity Your Recent Activity page contains a summary of all the recent activity that relates to your participation within a community. For example, this page lists all the ideas and comments you have posted to a community as well as the ideas you have voted on. You can view your Recent Activity page by clicking your community nickname located on the right side of the Ideas tab. Status An idea's status helps community members track the progress of the idea. For example, Under Review, Reviewed, Coming Soon, and Now Available are common status values an administrator can define and assign to ideas. An idea's status appears next to the idea's title for all community members to see. Top All Time Ideas On the Top All-Time subtab, ideas are sorted from most number of points to fewest. This allows you to see the most popular ideas in the history of your Salesforce CRM Ideas community. Vote, Idea In an ideas community, a vote means you have either promoted or demoted an idea. After you vote on an idea, your community nickname displays at the bottom of the idea's detail page to track that your vote was made. You can use your Recent Activity page to see a list of all the ideas you have voted on.
New Release Information

To stay current regarding new release information make use of: The official Salesforce.blog Salesforce Community IdeaExchange The Discover button is the quickest way to communicate new release information to end users.
Cees van der Sluis
Winter12
6|Page
ADM301 Exam Outline Details Answers Overview:

Introduction Answers is a feature of the Community application that enables users to ask questions and have community members post replies. Community members can then vote on the helpfulness of each reply, and the person who asked the question can mark one reply as the best answer. Best Answer When a member of an answers community asks a question and other community members post a reply, the asker can mark one of the replies as the best answer. The best answer then appears directly under the question (above the other replies). Identifying the best answer helps other community members with the same question quickly find the most relevant, useful information. Community Communities help organize ideas and questions into logical groups with each community having its own focus and unique ideas and questions. Professional Edition organizations can have only one internal ideas community. All other editions can have up to 50 communities shared between ideas and answers. Community Application The Community application includes the ideas and answers features. The Community app is available in the Force.com app menu. Data Category for Answers On the Answers tab, data categories allow users to classify questions in an answers community. For example, if you have an answers community for hardware products, your data categories may include laptops, desktops, and printers. Community members can quickly browse within a specific category to find answers to their questions. Administrators can use data categories to control access to questions. Idea Ideas are suggestions posted by the members of an ideas community. For example, if the focus of a particular community is Ideas for car features, an appropriate idea for that community might have the title Insulated cup holders that keep your beverage hot or cold. Or, if the focus of a particular community is Ideas for our company's employee benefits, an appropriate idea for that community might have the title On-site day care. Question An issue posted to an answers community. When a community member asks a question, other community members post replies to help resolve the question.
Cees van der Sluis
Winter12
7|Page

Reply The response to a question in an answers community. When community members reply to a question, the person who asked the question can mark one of the replies as the best answer to resolve and close the question. Vote, Reply In an answers community, a vote means you either like or dislike a reply to a question
CRM Content Overview:

Introduction With Salesforce CRM Content you can organize, share, search, and manage content within your organization and across key areas of the Salesforce application. Content can include all file types, from traditional business documents such as Microsoft PowerPoint presentations to audio files, video files, Web pages, and Google docs. What is Salesforce CRM Content? Salesforce CRM Content simplifies content management by incorporating user-friendly features into the following tasks: Organizing Rather than keep files in folders that make content difficult to find, Salesforce CRM Content stores files in fully searchable file repositories known as libraries. Administrators can create multiple libraries based on any classification, such as department name, job function, or team, then configure user permissions within the library to balance content access with security. Authors assign descriptive labels called tags to help classify and organize content across libraries. You can view a list of all content that belongs to a particular tag or filter search results based on a tag or tags. Salesforce CRM Content also provides personal libraries, which allow users to reduce the clutter on their desktops while using content-management benefits such as document search and version control. Searching The powerful Salesforce CRM Content search engine scans the entire body of the document as well as content properties such as the title, description, tags, categorization data, and author name. You can filter searches by featured content, file format, author, tags, libraries, or custom fields and then view the results with various levels of detail, providing an easy way to find relevant content quickly. If Chatter is enabled for your organization, you can also filter your search results by Chatter files. The smart bar graphic for downloads, comments, ratings, and subscribers allows you to compare documents within a search result set. Subscribing Once a file is located, subscribing to it ensures that you receive an email notification when new versions are published or changes are made to the file's properties. You can also subscribe to Cees van der Sluis Winter12 8|Page

authors, tags, and libraries, thus reducing the time spent searching for new or updated content. Notification emails will arrive real-time or once daily, depending on your preferences. Previewing In Salesforce CRM Content you do not need to download a large document to determine if its content is relevant to you. The content details page provides document details at a glance, including document title, author, description, tags, libraries, comments, votes, versions, subscribers, and downloads. If the document is a Microsoft PowerPoint, Word, Excel, or Adobe PDF file, you can preview the entire file in your browser without downloading it. Some Microsoft Office 2007 features don't display correctly in previews. Copy-protected PDFs can't be previewed. Contributing Uploading new or revised files in Salesforce CRM Content is fast and easy. During the upload process you choose a library and content type for your file or Web link, write a description, assign one or more tags, and fill out any customized fields that help categorize and define your content. Version management does not require checking files in and out, rather, you simply upload a new version of the file and Salesforce CRM Content maintains a version list accessible from the content details page. You can download past versions of a file and read all reason-for-change comments that an author may have included with a new version. Reviewing Usage and Providing Feedback Salesforce CRM Content provides several methods for determining whether content is valuable to readers. Featuring a piece of content increases its visibility in search results. Voting thumbs up or thumbs down on a file, Web link, or Google doc and adding comments allow you to participate directly in content improvement. You can also see who has subscribed to a file, link, or doc and how many times files have been downloaded. The Reports tab allows you to create standard or custom reports on Salesforce CRM Content data. If the content delivery feature is enabled, you can send content to colleagues, leads, and contacts and then track how often the content has been previewed or downloaded. Sharing Content in Salesforce Salesforce CRM Content is also integrated with leads, accounts, contacts, opportunities, cases, products, and custom objects. If Salesforce CRM Content functionality is enabled on the Opportunity tab, for example, Salesforce CRM Content uses the fields on the opportunity detail page to search for files that may be relevant to that opportunity. You can drill down in the search results as needed or run your own search and then attach one or more files to the opportunity. The most current version of the file will be available on the detail page for the life of the opportunity. Sharing Content in Salesforce Mobile Salesforce CRM Content is available in Salesforce Mobile. Users can share content with customers and colleagues from the mobile application when they're away from their desks. To enable Salesforce CRM Content for the mobile application, mobilize the content object and specify which content records are synchronized to the mobile device.
Cees van der Sluis
Winter12
9|Page

How Do I Access Salesforce CRM Content? The sections in this guide explain how to create Salesforce CRM Content users, define administrative settings in the Setup area, and configure libraries so contributors can begin publishing content. Licensed users can access Salesforce CRM Content by choosing Content from the Force.com Apps drop-down list. The Salesforce CRM Content application has three tabs: Libraries tab Clicking the Libraries tab opens the Libraries home page where you can access your personal library, choose a specific shared library to view or edit, analyze library usage and activity and, if applicable, create new libraries. The top of the page has several publishing-related options with which you can publish files, Web links, and Google docs as well as create custom content packs. See Managing Libraries in the Salesforce online help for more information. Content tab Clicking the Content tab displays files, content packs, Web links, and Google docs published in your Salesforce CRM Content libraries. If Chatter is enabled, files posted to Chatter groups and public Chatter files are also displayed on the Content tab. The top twenty most recently modified items are listed by default. You can search for content and then filter your results using several criteria. Click on a content item to open its content details page. See Searching for Content in the Salesforce online help for more information. Subscriptions tab Clicking the Subscriptions tab displays the Subscriptions home page, where you can view your Salesforce CRM Content subscriptions and toggle them off or on. Click the Content, Tags, Authors, or Libraries subtabs to view your subscriptions. Depending on your notification settings, you are notified of changes to your subscribed content via real-time emails or a once-daily email. See Viewing and Editing Content Subscriptions in the Salesforce online help for more information. Content Types Content types are the containers for custom fields in Salesforce CRM Content; content types determine which fields are available during the publishing process and how the fields display on the content details page. If multiple content types are available in a library, users select a content type after contributing files, content packs, Google docs, or Web links. Content Pack A content pack is a collection of related documents or files that are stored as a group in Salesforce CRM Content. For example, you may want to create a content pack with a product list, price quote, and contract to send to a particular customer. Any file in Salesforce CRM Content can be added to a content pack, from traditional business documents such as Microsoft PowerPoint presentations and Adobe PDF files, to audio files, video files, and Google docs. Using email or instant messaging, you can distribute the content pack to colleagues in your organization or leads and contacts outside your organization. The recipient of a content delivery can click a single URL to open a preview player with which he or she can preview and download the content. You can then view tracking information to see how often the content pack was viewed and which documents were downloaded. Cees van der Sluis Winter12 10 | P a g e

Tags In Salesforce CRM Content, tags are descriptive labels that help classify and organize content. Contributors can assign tags to their files, content packs, Google docs, or Web links, thus enabling all library members to browse for content by tag. The tagging rule in a library determines how contributors can tag content; for example, the restricted-tagging rule does not allow contributors to create new tags. Library tagging rules are optional. By default, library contributors can enter any tag. Tagging Rules There are three different tagging rules: Open Tagging: This rule places no restrictions on tagging. Contributors can enter any tag when publishing or editing content. While a tag is typed, Salesforce CRM Content auto suggests tags based on the contributor's recently used tags and the Popular Tags list. Guided Tagging: This rule also enables contributors to enter any tag when publishing or editing content, but contributors are also offered a list of suggested tags. If you select Guided Tagging, the next step prompts you to enter the suggested tags that you want to recommend to library contributors. Restricted Tagging: This rule requires contributors to choose from the list of suggested tags. If you select Restricted Tagging, the next step prompts you to enter the list of suggested tags.
Cees van der Sluis
Winter12
11 | P a g e
Force.com (Platform as a Service)

Force.com platform
Force.com is a platform for creating and deploying applications for the social enterprise. Because there are no servers or software to buy or manage, you can focus solely on building apps that include built-in social and mobile functionality, business processes, reporting, and search. Your apps run on a secure, proven service that scales, tunes, and backs up data automatically.
The Cloud computing model
Cees van der Sluis
Winter12
12 | P a g e
ADM301 Exam Outline Details Types of Applications suitable for Force.com
Salesforce localization
The concepts used when implementing Salesforce Localization includes: Implement the Locale in the client org, including changing defaults for Company and Users. o Timezone o Location o Language o Currency Work with Salesforce Support to enable Multiple Currencies Translate the customizations using the Translation Workbench Enter or translate any data, setup multiple currencies, change defaults for currencies Test the translation in a Sandbox or Developer Org How to support a global implementation: Delegated administration Advanced Currency Management Territory Management Regional Pricebooks Translation Workbench
Cees van der Sluis
Winter12
13 | P a g e

Localization: Customization and Support What to keep local: Translations Report and Dashboard names Field names Picklist values What to keep central: Sharing model Data integration / management Application customization Maintain strategic deals in English, so execs can easily access Define a corporate currency for easy management reporting
Cees van der Sluis
Winter12
14 | P a g e
Application Essentials
Objects, Fields, Relationships
Custom objects are custom database tables that allow you to store information unique to your organization. For example, your organization may want to create a custom object called Quotes to store data for your companys sales quotes. After you define a custom object, you can: Create custom fields. For the total number of custom fields you can create, see Salesforce Editions and Limits. Associate the custom object with other records and display the custom object data in custom related lists. For more information, see Overview of Relationships. Track tasks and events for custom object records Build page layouts Customize the search results and the custom object fields that display in them Create a custom tab for the custom object Create reports and dashboards to analyze custom object data Share your custom objects, custom tabs, custom apps, and any other related components with other Salesforce users on Force.com AppExchange. See Overview of Packages. Import custom object records Set up a queue to distribute ownership of custom object records Custom fields will enable you to store the information that is important to your organization. Before you begin, determine the type of custom field you want to create. You can create many different custom field types, including lookup, master-detail, and hierarchical relationships. Use relationships to associate an object with other objects in Salesforce. For example, a relationship can link custom object records to standard object records in a related list, such as linking a custom object called Bugs to cases to track product defects associated with customer cases. You can define different types of relationships by creating custom relationship fields on an object. Before you begin creating relationships, determine the type of relationship that suits your needs. There are different types of relationships between objects in Salesforce. Their differences include how they handle data deletion, record ownership, security, and required fields in page layouts: Master-detail This type of relationship closely links objects together such that the master record controls certain behaviors of the detail and subdetail record. For example, you can define a twoobject master-detail relationship, such as AccountExpense Report, the extend the relationship to subdetail records, such as AccountExpense ReportExpense Line Item. You can then perform operations across the masterdetailsubdetail relationship.
Cees van der Sluis
Winter12
15 | P a g e

Behaviors of master-detail relationships include: When a master record is deleted, the related detail and subdetail records are also deleted. The Owner field on the detail and subdetail records is not available and is automatically set to the owner of the master record. Custom objects on the detail side of a masterdetail relationship can't have sharing rules, manual sharing, or queues, as these require the Owner field. The security settings for the master record control the detail and subdetail records. The master-detail relationship field (which is the field linking the objects) is required on the page layout of the detail and subdetail records. The master object can be a standard object, such as Account or Opportunity, or a custom object. As a best practice, don't exceed 10,000 child records for a master-detail relationship. Many-to-many You can use master-detail relationships to model many-to-many relationships between two standard objects, two custom objects, or a custom object and a standard object. A many-tomany relationship allows each record of one object to be linked to multiple records from another object and vice versa. For example, you may have a custom object called Bug that relates to the standard case object such that a bug could be related to multiple cases and a case could also be related to multiple bugs. Lookup This type of relationship links two objects together, but it has no effect on record ownership or security, and the lookup relationship field is not required in the page layout. Use lookup relationships to: Link two different objects, custom or standard. Link an object with itself, custom or standard (with the exception of the user object; see Hierarchical). For example, you may want to link a custom object called Bug with itself to show how two different bugs are related to the same problem. Hierarchical This type of relationship is a special lookup relationship available only for the user object. It allows users to use a lookup field to associate one user with another that does not directly or indirectly refer to itself. For example, you can create a custom hierarchical relationship field to store each user's direct manager.
Cees van der Sluis
Winter12
16 | P a g e
ADM301 Exam Outline Details Formula Overview:

What is a formula? A formula is an algorithm that derives its value from other fields, expressions, or values. The value of a formula is not stored. Instead, the formula is calculated each time the value is displayed. Formulas can be used in: Custom fields Default field values Validation rules Filter criteria Field updates Custom summary formulas Custom buttons and links Visualforce pages Methodology for writing formulas: Step 1: Describe the business requirement Step 2: Create simple statements Step 3: Write the formula Formulas can be used for the following purposes: Creating an image formula, for example: display a coloured flag regarding the status of an Account IMAGE(...) Creating a calculation formula, for example: how many days is a Case open IF(...)
Creating a validation rule formula, for example, a user cannot save an Opportunity when the Opportunity Stage is Closed Lost and the field Reason Lost is empty AND(...)
Creating validation rule to prevent unwanted changes, for example the Amount of an Opportunity cannot be changed when an Opportunity is set to Closed Won AND(IsCloded, ISCHANGED(Amount))
Categorizing data with formulas IF(....IF(...)IF(...)) or CASE(...)
Cees van der Sluis
Winter12
17 | P a g e
Creating a formula field that spans objects, for example show the Candidate details (first name, last name, phone number and education level) on the Job Application
Creating a custom summary formula, for example show how sales reps are performing month over month (growth percentage) Validating data against a table, for example match the Zip Code against the State entered
Custom Buttons and Links

Before creating a custom button or link, determine what action you want to occur when a user clicks it. Consider a Visualforce page if you want the button or link to launch a custom page or other code. To define custom buttons and links: 1. Select Your Name | Setup | Customize, select the appropriate tab or users link, and choose Buttons and Links. Custom buttons are not available on the user object or custom home pages. Custom buttons and links are available for activities under the individual setup links for tasks and events. However, you can override a button that applies to both tasks and events by clicking Your Name | Setup | Customize | Activities | Activity Buttons. For custom objects, click Your Name | Setup | Create | Objects, and select one of the custom objects in the list. 2. Click New from the Custom Buttons and Links section. 3. Enter the following attributes: Attribute Name Description
Label Name The text that displays on user pages for the custom button or link. The unique name for the button or link used when referenced from a merge field. This name can contain only underscores and alphanumeric characters, and must be unique in your organization. It must begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores. In a packaging context, a namespace prefix is a one to 15-character
Namespace Prefix
Cees van der Sluis
Winter12
18 | P a g e

alphanumeric identifier that distinguishes your package and its contents from packages of other developers on AppExchange. Namespace prefixes are case-insensitive. For example, ABC and abc are not recognized as unique. Your namespace prefix must be globally unique across all Salesforce organizations. It keeps your managed package under your control exclusively. Protected components cannot be linked to or referenced by components created in a subscriber organization. A developer can delete a protected component in a future release without worrying about failing installations. However, once a component is marked as unprotected and is released globally, the developer cannot delete it. Text that distinguishes the button or link from others. This displays only to administrators when setting up buttons and links. Determines where the button or link is available on page layouts: Detail Page Link Select this option if you want to add the link to the Custom Links section of your page layouts. Detail Page Button Select this option if you want to add the custom button to a record's detail page. You can only add detail page buttons to the Button Section of a page layout. List Button Select this option if you want to add the custom button to a list view, search result layout, or related list. You can only add list buttons to the Related List Section of a page layout or the List View and Search Result layouts. For list buttons, Salesforce automatically selects a Display Checkboxes (for Multi-Record Selection) option that includes a checkbox next to each record in the list, allowing users to select the records they want applied to the action on the list button. Deselect this option if your custom button does not require the user to select records such as one that quickly navigates the user to another page. Choose the outcome of clicking the button or link. When applicable, some settings have default values. For example, if you choose Display in new window, the default height of a new window is 600 pixels. To change these settings, see Editing Window Open Properties. Choose whether to use a URL, s-control, JavaScript action, or Visualforce page as the content of the button or link. To use an scontrol, choose Custom S-Control, and select the s-control from the drop-down list. To use a URL, select URL, and enter the link below in the text area box exactly as it would appear in the address bar of a Web browser. To execute JavaScript code when the button or link is activated, select OnClick JavaScript, and enter the code in the text area box below. To use a Visualforce page, select Visualforce Page, and choose the page from the drop-down list. Enter the content of the button or link for buttons and links of type URL or OnClick JavaScript: To insert a field, choose the field type in the Select Field Type drop-down list, and choose one of the fields listed in the Insert Field drop-down list. To insert activity merge fields, select Event or Task from the Select Field Type drop-down list. To insert an operator, choose the appropriate operator icon from the Insert Operator drop-down list. Use the examples in Operators and Functions.
Protected Component
Description Display Type
Behavior
Content Source
Content
Cees van der Sluis
Winter12
19 | P a g e

To insert a function, double-click its name in the list, or select it and click Insert Selected Function. To filter the list of functions, choose a category from the Functions drop-down list. Select a function and click Help on this function to view a description and examples of formulas using that function. Encoding setting that defaults to Unicode (UTF-8). Change the default encoding setting if the target of a link requires data in a different format. This is available if your Content Source is URL.
Link Encoding
4. Optionally, click Check Syntax to validate all Salesforce merge fields and functions. 5. Click Save when you are finished. Click Quick Save to save and continue editing. Click Preview to view the URL specified. Click Cancel to quit without saving your content. 6. Edit the page layout for the appropriate tab or search layout to display the new button or link. If you add a custom link for users, it is automatically added to the Custom Links section of the user detail page. Detail page buttons can only be added to the Button Section of a page layout. 7. Optionally, set the window properties if you prefer the link or button opening using different settings than the user's default browser settings.
Usage of Custom Buttons

There is a variety of possibilities to use a Custom buton, for example: Displaying Alerts Getting Record Ids Mass Delete Passing Record IDs to an External System Reopening Cases
Button Overrides and Visualforce

It is possible to override the action of a standard button on a record page to augment standard Salesforce behaviour, for example: Override the New button to display and alternative form for data entry Override the Edit button to dynamically restrict Edit privileges The action performed by the override is determined by a Visualforce page - usually in conjunction with a Visualforce controller (Apex code)
Cees van der Sluis
Winter12
20 | P a g e
Security and Access

Sharing Model Overview:
Sharing Model Elements: Profiles Roles Hierarchy Record Types Page Layouts Field Level security Record Types Hours and IP Addresses An organization's sharing model sets the default access that users have to each others data. There are four sharing models: Private: Only the record owner, and users above that role in the hierarchy, can view, edit, and report on those records. For example, if Tom is the owner of an account, and he is assigned to the role of Western Sales, reporting to Carol (who is in the role of VP of Western Region Sales), then Carol can also view, edit, and report on Tom's accounts. Public Read Only: All users can view and report on records but not edit them. Only the owner, and users above that role in the hierarchy, can edit those records. For example, Sara is the owner of ABC Corp. Sara is also in the role Western Sales, reporting to Carol, who is in the role of VP of Western Region Sales. Sara and Carol have full read/write access to ABC Corp. Tom (another Western Sales Rep) can also view and report on ABC Corp, but cannot edit it. Public Read/Write: All users can view, edit, and report on all records. For example, if Tom is the owner of Trident Inc., all other users can view, edit, and report on the Trident account. However, only Tom can alter the sharing settings or delete the Trident account. Public Read/Write/Transfer: All users can view, edit, transfer, and report on all records. Only available for cases or leads. For example, if Alice is the owner of ACME case number 100, all other users can view, edit, transfer ownership, and report on that case. But only Alice can delete or change the sharing on case 100.
Cees van der Sluis
Winter12
21 | P a g e

Profiles: A profile defines a users permission to perform different functions within salesforce.com. Profiles also control the following: Which page layouts the user sees The field-level security access that the user has to view and edit specific fields Which tabs the user can view Which record types are available to the user The hours and IP addresses from which the user can log in Administrators, and users with the "Manage Users" permission, can create, edit, and delete profiles By making use of the possibility for a Profile to restrict the Login Hours you are able to prevent users from logging in to the system during maintenance periods Notes on User Roles Every user must be assigned to a role, or their data will not display in opportunity reports, forecast rollups, and other displays based on roles. All users that require visibility to the entire organization should be assigned the highest level in the hierarchy. It is not necessary to create individual roles for each title at your company, rather you want to define a hierarchy of roles to control access of information entered by users in lower level roles. When you change a user's role, any relevant sharing rules are reevaluated to add or remove access as necessary.
Role Controls level visibility users have to the organizations data May have many users but a single user will only have one role
Role Hierarchy Controls data visibility Controls record roll up for reporting Allow users access to records owned by users below them in the hierarchy, regardless of OWD settings Does not necessary correspond to the companys employee organization chart
Record Types If your organization uses record types, edit the record type to modify which pick list values are visible for the record type. You can set default pick list values based upon the record type for various divisions.
Cees van der Sluis
Winter12
22 | P a g e

Field Level Security Field-level security settings let administrators restrict users. access to view and edit specific fields on detail and edit pages and in related lists, list views, reports, Offline Edition, search results, email and mail merge templates, Custom Links, and when synchronizing data. The fields that users see on detail and edit pages are a combination of page layouts and field-level security settings. The most restrictive field access settings of the two always apply. For example, if a field is required in the page layout and read-only in the field-level security settings, the field-level security overrides the page layout and the field will be read-only for the user. Controlling Data Access Data Access is based on: Record ownership OWD (restrictive) Roles Sharing Permissions and User interface for accessible data is based on Profile settings.
What are the salesforce.com audit levels?

Within the salesforce.com system, the creator and last updater, as well as timestamps, are recorded for every record. All logins, both successful and unsuccessful, are recorded for retrieval by the customer's organization administrator. Logoffs are not records, as they cannot be determined in a web architecture. The setup audit trail history helps you track the recent setup changes that you and other administrators have made to your organization. This can be especially useful in organizations with multiple administrators. The setup audit trail history tracks the following types of changes: Company information changes Weekly data export requests Multiple currency setup changes User, role, and profile changes Public groups, organization-wide sharing, and sharing rule changes Password policy changes Mass delete, mass transfer, and import wizard use Company message changes Page layout changes Field-level security changes Changes to lead settings, lead assignment rules, and lead queues Changes to support settings, business hours, case assignment and escalation rules, and case queues Any changes made by salesforce.com Customer Support at your request Cees van der Sluis Winter12 23 | P a g e

Any tabs that you have renamed including tabs that you reset to the original tab name
System Debug Log A debug log records database operations, system processes, and errors that occur when executing a transaction or while running unit tests. The system generates a debug log for a user every time that user executes a transaction that is included in the filter criteria. It will enable you to view a real-time trace of automated processes or up to 20 persisted logs Debug logs can contain information about: Database changes HTTP callouts Apex errors Resources used by Apex Automated workflow processes, such as: o Workflow rules o Assignment rules o Approval processes o Validation rules There are many different types of application logs collected. Server access is logged, network access is logged, firewalls log traffic, network intrusion detection systems log traffic, etc. Logs are typically reviewed daily. The logs are collected by various tools such as HP OpenView, CiscoWorks, etc., and alarms are configured to alert the systems engineering team to various activities. Firewalls and IDS systems are configured with automated syslog notifications for key events. Logs are archived and are currently stored for a minimum of 6 months. These logs are not available to customers. Limited forensic evidence, if needed, is available from the web or application logs and can be provided at salesforce.com for standard consulting fees. We offer a weekly export service for those customers that have a requirement to have a local backup copy of their data or a set of data they can import into another system such as an ERP system. The organization administrator for an organization which subscribes to the WES can request a copy of their organizations data. Once the data is assembled into a zip file, the organization administrator is notified via email that their data is ready for secure download (SSL) from within the application. The zip file contains a number of .csv files, each representing a major entity type from the application, and it includes primary and foreign keys so that the information can be reassembled in another relational system. If auditing needs to be verified and maintained for regulatory or advanced security environments the sforce API supports data replication, which allows you to store and maintain a local, separate copy of your organization's pertinent salesforce.com data including the META data (logins etc) for specialized uses, such as data warehousing, data mining, custom reporting, analytics, integration with other applications, and so on. Data replication provides you with local control and the ability to run large or ad hoc analytical queries across the entire data set without transmitting all that data across the network.
Cees van der Sluis
Winter12
24 | P a g e
ADM301 Exam Outline Details Delegated Administration Overview: Delegating Administrative Duties
Delegated administrators can perform the following tasks: Creating and editing users and resetting passwords for users in specified roles and all subordinate roles, including setting quotas, creating default sales teams, and creating personal groups for those users Unlocking non-portal users Assigning users to specified profiles Logging in as a user who has granted login access to their administrator Managing custom objects created by an administrator Notes on Delegated Administration of Custom Objects: Delegated administrators can customize nearly every aspect of the custom object, including creating a custom tab for it. However, they cannot create or modify relationships on the object or set organization-wide sharing defaults. Delegated administrators need to have access to custom objects if they need to access the merge fields on those objects from formulas.
Territory Management Overview:

Territory management is an account sharing system that grants access to accounts based on the characteristics of the accounts. It enables your company to structure your Salesforce data and users the same way you structure your sales territories. Particularly if your organization has a private sharing model, you may need to grant users access to accounts based on criteria such as zip code, industry, revenue, or a custom field that is relevant to your business. You may also need to generate forecasts for these diverse categories of accounts. Territory management solves these business needs and provides a powerful solution for structuring your users, accounts, and their associated contacts, opportunities, and cases. Key benefits of territory management include: The ability to use account criteria to expand a private sharing model. Support for complex and frequently changed sales organization structures. Support for transferring users between territories, with the option to retain opportunities. Multiple forecasts per user, based on territory membership. Territory-based sales reports. What is a Territory? A territory is a flexible collection of accounts and users where the users have at least read access to the accounts, regardless of who owns the account. By configuring territory settings, users in a territory can be granted read, read/write, or owner-like access (that is, the ability to view, edit, transfer, and delete records) to the accounts in that territory. Both accounts and users can exist in multiple territories. You can manually add accounts to territories, or you can define account assignment rules that assign accounts to territories for you.
Cees van der Sluis
Winter12
25 | P a g e

Not only can you control access to accounts for users in each territory, you can also control users' access to the opportunities and cases associated with the accounts in the territory, regardless of who owns the records. What is a Territory Hierarchy? Territories exist in a hierarchy which you can set up with as many nested levels as you wish. For example, you could create a top-level territory named Worldwide Sales that has the child territories North America, Europe/Middle East, Latin America, Africa, and Asia/Australia. North America might have the child territories Canada and United States. United States might have the child territories Western, Central, Southern, and Eastern. Finally, Western might have the child territories California, Oregon, Washington, Nevada, Arizona, and Utah. Note that territory hierarchies do not have to be focused on geography; they can be defined however you like. How Do Territories Affect Forecasting? When you enable territory management for your organization, your forecast data is derived from the opportunities that are associated with the accounts in your territories. Users will have a different forecast for each territory to which they are assigned. For example, if you are assigned to both California and Arizona, you will have one forecast for the opportunities you have in California, and another forecast for the opportunities you have in Arizona. Set up Territory Management Use the following steps to deploy territory management for your Salesforce organization. For the most successful and complete results, perform the following procedures in order: 1. Prerequisites for Enabling Territory Management a. Enable Customizable Forecasting 2. Enabling Territory Management. a. Enable Territory Management, your organization's current forecast hierarchy and forecast data are automatically copied to the territory hierarchy b. Enable Territory Management from Scratch, all pre-existing forecast data is deleted and an empty territory hierarchy is created. 3. Configuring Territory-Related Settings 4. Building a Territory Hierarchy 5. Assigning Users to Territories 6. Assigning Accounts to Territories
Cees van der Sluis
Winter12
26 | P a g e

Are the territory hierarchy and the role hierarchy different? Yes. The territory hierarchy and the role hierarchy are independent. See the following comparison: Territory Hierarchy
Is available by contacting salesforce.com Determines forecasts Supports assigning a user to multiple territories Affects account and opportunity reports Grants access to records regardless of ownership. Users receive whatever access is most permissive across both hierarchies.
Role Hierarchy
Is available by default Has no impact on forecasting when territory management is enabled Supports assigning a user to only one role Affects all other reports Grants access to records based on ownership. Users receive whatever access is most permissive across both hierarchies.
Record Types versus Page Layouts

Record types allow you to offer different business processes, picklist values, and page layouts to different users based on their profiles. Record types can be used in various ways, for example: Create record types for opportunities to differentiate your regular sales deals from your professional services engagements and offer different picklist values for each. Create record types for cases to display different page layouts for your customer support cases versus your billing cases. Page Layouts define which fields users can view and edit when entering data for a custom object record. You can use the default page layout that is created automatically when you create a custom object. You can also build your own page layout with related lists and custom links. If you do not use any page layout with your custom object, you can still interact with it by using the Force.com API to manage custom data or build a custom user interface. In the enhanced profile user interface, Record Types and Page Layout Assignments settings determine the record type and page layout assignment mappings that are used when users view records. They also determine which record types are available when users create or edit records. To specify record types and page layout assignments: 1. Click Your Name | Setup | Manage Users | Profiles. 2. Select a profile. 3. In the Find Settings... box, enter the name of the object you want and select it from the list. 4. Click Edit. 5. In the Record Types and Page Layout Assignments section, make changes to the settings as needed. Setting Description
Record Types Lists all existing record types for the object. --Master-- is a system-generated record type that's used when a record has no custom record type associated with it. When -Master-- is assigned, users can't set a record type to a record, such as during record creation. All other record types are custom record types. The page layout to use for each record type. The page layout determines the buttons, fields, related lists, and other elements
Page Layout Assignment
Cees van der Sluis
Winter12
27 | P a g e

that users with this profile see when creating records with the associated record type. Since all users can access all record types, every record type must have a page layout assignment, even if the record type isn't specified as an assigned record type in the profile. Record types that are checked in this column are available when users with this profile create records for the object. If --Master-is selected, you can't select any custom record types; and if any custom record types are selected, you can't select --Master--. The default record type to use when users with this profile create records for the object.
Assigned Record Types
Default Record Type
The Record Types and Page Layout Assignments settings have some variations for the following objects or tabs. Object or Tab
Accounts
Variation
If your organization uses person accounts, the accounts object additionally includes Business Account Default Record Type and Person Account Default Record Type settings, which specify the default record type to use when the profile's users create business or person account records from converted leads. The cases object additionally includes Case Close settings, which show the page layout assignments to use for each record type on closed cases. That is, the same record type may have different page layouts for open and closed cases. With this additional setting, when users close a case, the case may have a different page layout that exposes how it was closed. You can't specify custom record types for the home tab. You can only select a page layout assignment for the --Master-- record type.
Cases
Home
6. Click Save.
Cees van der Sluis
Winter12
28 | P a g e
Implementing Business Processes

Workflow rules
Introduction Your sales force operates more efficiently with standardized internal procedures and automated business processes. Set up Salesforce to automatically perform these procedures and processes based on your organizations needs. Workflow Rule A workflow rule sets workflow actions into motion when its designated conditions are met. You can configure workflow actions to execute immediately when a record meets the conditions in your workflow rule, or set time triggers that execute the workflow actions on a specific day. If a workflow action has not executed yet, you can view and modify it in the Workflow Queue. See Managing Workflow Rules to get started using workflow rules. For a list of the maximum number of rules allowed in each organization, see Salesforce Editions and Limits. Flow A flow starts out as a process or decision diagram created in the Flow Designer. Once uploaded and run in Salesforce, it becomes an application for navigating users through a series of screens. See About Visual Workflow to get started using flows. Workflow and Approval Actions Workflow and approval actions consist of email alerts, tasks, field updates, and outbound messages that can be triggered by a workflow rule or approval process. Email Alert Email alerts are workflow and approval actions that are generated using an email template by a workflow rule or approval process and sent to designated recipients, either Salesforce users or others. See Managing Email Alerts to get started using email alerts. Field Update Field updates are workflow and approval actions that specify the field you want updated and the new value for it. Depending on the type of field, you can choose to apply a specific value, make the value blank, or calculate a value based on a formula you create. See Managing Field Updates to get started using field updates. Task Assigns a task to a user you specify. You can specify the Subject, Status, Priority, and Due Date of the task. Tasks are workflow and approval actions that are triggered by workflow rules or approval processes.
Cees van der Sluis
Winter12
29 | P a g e

Outbound Message An outbound message is a workflow, approval, or milestone action that sends the information you specify to an endpoint you designate, such as an external service. An outbound message sends the data in the specified fields in the form of a SOAP message to the endpoint. Workflow actions execute in the following order: Field Update Task Emails Outbound messaging Workflow rules are not fired retroactively. In other words, if you create a rule now, the rules are not applied to previously created records. The same holds true for time-based workflow rules. For example, when you create an opportunity reminder rule, it does not run against existing opportunities. The new rule only applies to records created or updated after the rule is activated. The time-based workflow feature leverages the existing workflow engine. The actions for a workflow are now grouped into two sections: immediate actions and time-dependent actions. The basic rule configuration is the same, but for time-based rules, you configure time-triggers in the timedependent actions section. Each time trigger can execute one or more workflow actions. You cannot configure time-dependent actions for workflow rules for which the evaluation criteria is set to "Every time a record is created or edited." Time-dependent actions can automatically be queued again if the record is updated and you set the evaluation criteria to be "When a record is created, or when a record is edited and did not previously meet the entry criteria." You will be able to monitor the Time-Based Workflow queue via Setup | Monitoring | Time-Based Workflow. When Salesforce triggers a workflow rule that has time-dependent actions, use the workflow queue to view pending actions and cancel them if necessary.
Cees van der Sluis
Winter12
30 | P a g e
ADM301 Exam Outline Details Approval Proces

Introduction An approval process is an automated process your organization can use to approve records in Salesforce. An approval process specifies the steps necessary for a record to be approved and who must approve it at each step. A step can apply to all records included in the process, or just records that have certain attributes. An approval process also specifies the actions to take when a record is approved, rejected, recalled, or first submitted for approval. Your business runs more efficiently with automated processes. For example, you may already have workflow rules that automatically send email alerts or assign tasks based on your internal processes. Approvals take automation one step further, allowing you to specify a sequence of steps that are required to approve a record. For example, your organization may have a two-step process for approving expenses: submitted expenses that are less than $50 are automatically approved, those over $50 must be approved by a manager, and those over $5,000 must also be approved by a Vice President. In this example, your approval process would specify the following: If an expense record is submitted for approval, lock the record so that users cannot edit it and change the status to Submitted. If the amount is $50 or less, automatically approve the request. If the amount is greater than $50, send an approval request to the direct manager. If the amount is greater than $5,000 and the first approval request is approved, send an approval request to the Vice President. If all approval requests are approved, change the status to Approved and unlock the record. If any approval requests are rejected, change the status to Rejected and unlock the record. Approval Request An email notifying the recipient that a record was submitted for approval and his or her approval is requested. Approval Steps Approval steps assign approval requests to various users and define the chain of approval for a particular approval process. Each approval step specifies the attributes a record must have to advance to that approval step, the user who can approve requests for those records, and whether to allow the delegate of the approver to approve the requests. The first approval step in a process also specifies the action to take if a record does not advance to that step. Subsequent steps in the process also allow you to specify what happens if an approver rejects the request. Assigned Approver The assigned approver is the user responsible for approving an approval request. . Cees van der Sluis Winter12 31 | P a g e

Delegated Approver A delegated approver is a user appointed by an assigned approver as an alternate for approval requests. Delegated approvers can't reassign approval requests; they can only approve or reject approval requests. Email Approval Response The email approval response feature gives users the ability to approve or reject email approval requests by replying to the email. The first line of the email body may contain one of the following words: approve approved yes reject rejected no Periods and exclamation marks are also accepted at the end of the word. You can also optionally add comments in the second line of the email body. Users can still click a link in the email to access the approval page as well. This feature is especially useful for organizations with users who receive approval requests on mobile devices. Initial Submission Actions Initial submission actions are the actions that occur when a user first submits a record for approval. By default, an action to lock the record runs automatically on initial submission. Initial submission actions can include any approval actions such as email alerts, field updates, tasks, or outbound messages. For example, an initial submission action can update a custom approval status field to In Progress. Final Approval Actions Final approval actions are the actions that occur when all required approvals have been given for a record. Final approval actions can include email alerts, field updates, tasks, or outbound messages. For example, a final approval action can change the status to Approved and send an email notification. Final Rejection Actions Final rejection actions are the actions that occur when an approver rejects the request and it goes to the final rejection state. Final rejection actions can include email alerts, field updates, tasks, or outbound messages. For example, a final rejection action can change the status to Rejected, send an email notification, and unlock the record so that users can edit it before resubmitting.
Cees van der Sluis
Winter12
32 | P a g e

Outbound Message An outbound message is a workflow, approval, or milestone action that sends the information you specify to an endpoint you designate, such as an external service. An outbound message sends the data in the specified fields in the form of a SOAP message to the endpoint. Recall Actions Recall actions are the actions that occur when a submitted approval request is recalled. By default, an action to unlock the record runs automatically on recall. Recall actions can include email alerts, field updates, tasks, or outbound messages. For example, a recall action can change the status of a request from In Progress to Not Submitted. Record Locking Record locking is the process of preventing users from editing a record, regardless of field-level security or sharing settings. Salesforce automatically locks records that are pending approval. Users must have the Modify All object-level permission for the given object, or the Modify All Data permission, to edit locked records. The Initial Submission Actions, Final Approval Actions, Final Rejection Actions, and Recall Actions related lists contain Record Lock actions by default. You cannot edit this default action for initial submission and recall actions. You can still add campaign members to campaigns locked for approval. Some examples of common approval processes to help you get started creating your own: PTO Requests, most companies require employees to file a PTO (Paid Time Off) request and have their manager approve it. This can be achieved by setting up an automated simple onestep PTO request process using Salesforce. Expense Reports, If your company requires that employees file expense reports for managers to approve, automate this process in Salesforce. For example create a two-step expense report approval process for all employees in your headquarters office. It specifies that expenses less than $50.00 are automatically approved, those $50 and over require manager approval, and those over $5,000 require additional approval from two VPs. This example highlights the else option, as well as the parallel approvals feature. Discounting Opportunities, for example Opportunities that are discounted more than 40% require a CEO approval. You can use this example to create a one-step approval process. Job Candidates, when your company interviews candidates for a position, you may have several levels of approval before you can send an offer letter. You can use this example to create a three-step approval process that requires approval from multiple levels of management.
Cees van der Sluis
Winter12
33 | P a g e
ADM301 Exam Outline Details In what order are automation rules and Apex triggers processed?
The order automation rules are processed is: System Validation Rules Custom Validation Rules Assignment rules Auto-response rules Workflow rules Escalation rules There is no way to control the order of execution within each group above. Workflow field updates that run based on an approval process or time-dependent action do not trigger any rules. Formula fields do not execute in this way. They calculate and display their results real-time whenever the field is accessed in any way. So for example if a Workflow Rule uses a Formula Field in its criteria or formula, the formula field is evaluated when the Workflow Rule criteria is checked.
Process Visualizer Overview

You can use the Process Visualizer to: Display a flowchart of each saved approval process Improve communication about the approval process and gain buy-in from step owners Reinforce your company's policies by documenting the decisions you reached when the approval process was designed Print an annotated version of the approval process, where numbers added to the diagram correspond to details in a table, which is included in the printable view Share approval process diagrams by saving annotated versions as PDF files (requires an Adobe PDF print driver) Help you quickly locate key details by searching multi-step or complex diagrams for matching text Help you visualize and understand graphically: o The steps necessary for a record to be approved o The designated approvers for each step o The criteria used to trigger the approval process o The specific actions to take when a record is approved, rejected, recalled, or first submitted for approval Before you can use the Process Visualizer, you must: Enable or download the Adobe Flash Player plugin, version 9.0.115 or later, in your browser Have at least one approval process defined in your organization Each approval process diagram is for viewing purposes only. You cannot update an approval process from the Process Visualizer. After saving your changes to the approval process, click View Diagram to view the updates or, if the Process Visualizer window is still open, click Refresh.
Cees van der Sluis
Winter12
34 | P a g e
Managing Data
Data Loader Overview
Data Loader is a client application for the bulk import or export of data. Use it to insert, update, delete, or export Salesforce records. When importing data, Data Loader reads, extracts, and loads data from comma separated values (CSV) files or from a database connection. When exporting data, it outputs CSV files. You can use Data Loader in two different ways: User interfaceWhen you use the user interface, you work interactively to specify the configuration parameters, CSV files used for import and export, and the field mappings that map the field names in your import file with the field names in Salesforce. Command lineWhen you use the command line, you specify the configuration, data sources, mappings, and actions in files. This enables you to set up Data Loader for automated processing. Use Data Loader when: You need to load 50,000 to 5,000,000 records. If you need to load more than 5,000,000 records, we recommend you work with a Salesforce.com partner. You need to load into an object that is not yet supported by the import wizards. You want to schedule regular data loads, such as nightly imports. You want to export your data for backup purposes. Your organization can generate backup files of your data on a weekly or monthly basis depending on your edition. You can export all of your organization's data into a set of comma-separated values (CSV) files. Data Loader export wizard can be used to extract data from any Salesforce object. When you export, you can choose to include (Export All) or exclude (Export) soft-deleted records. You can use a SOQL relationship query to include fields from a related object.
How can I identify the attachments in my Data Export?

When the Data Export file is provided, the attachments are listed with the associated IDs. These IDs do not have the extensions to identify what type of file you are working with. Within the export file is the attachment .csv file which contains the relative information for the attachments. This file will provide: 1. The IDs as seen within the ZIP file. 2. The Name as it existed in salesforce.com. 3. The extension. 4. The ID of the record it was related to within salesforce.com.
Cees van der Sluis
Winter12
35 | P a g e
ADM301 Exam Outline Details How to Export attachments?

The easiest way to download all the attachments that are stored in your salesforce.com account is to follow the instructions below. As an Administrator, you can: 1. Click on: Setup | Admin Setup | Data Management | Storage Usage. 2. Scroll down in that screen and locate the Top Files by Storage Utilization section. 3. From there, the Administrator can drill into each attachment and click on them to open with the appropriate program or save them to disk as prompted. Attachments are also included in the Weekly Export Service. This service allows Administrators to request a weekly download of all salesforce.com data including attachments. Please contact your Account Executive for more information.
Salesforce.com Data Export Service

Salesforce.com recommends that all customers back-up their salesforce.com data. All customers are advised to perform a weekly export. An export should be generated prior to any data project performed by an organization via the import wizards or DataLoader imports, updates, or deletions). A weekly export service is available to customers, and is outlined below. The weekly export service allows organizations to export a complete set of their salesforce data including all attachments for archival purposes. A system administrator can request a data export once every seven (7) days. The salesforce.com service will automatically extract the organization's data into compressed .csv data files and send an email confirmation to the administrator requesting the export. The email will contain a web address to a secure page, from which the administrator can download the series of compressed data files. To request a data export, follow the steps listed below: 1. Click on: Setup | Administration Setup | Data Management | Data Export. 2. Select the "Include attachments" check box (if desired). 3. Select any data that you would like to include by checking the box next to the name of the object. Selecting the "Include all data" box will include data from all tables. 4. Click the "Data Export" button. A confirmation email will be sent when the export has completed, with a link to the export files, as mentioned above. The weekly export service is available for all Enterprise Edition customers, and is included in your license fees. The weekly export service is available to Professional Edition customers as an add-on service, for $50/month.
Cees van der Sluis
Winter12
36 | P a g e
ADM301 Exam Outline Details Data Definitions:

Data Migration: The process of transferring data from one repository to another. Data Management: Systematic collection, organization, and analysis of data. Data Enrichment: Improving existing data by linking it to additional data sources. Data Cleansing: creating format consistency by removing bad data and consolidating data sources. Data De-duplication: Identifying and merging duplicate records. The Data Migration Process: In the data migration process data is extracted, transformed, mapped to the associated fields and then loaded to the system. The Data Management process: In the data management process the data is retrieved from the system and identified. Following this the data is cleansed and is then maintained on the system.
Cees van der Sluis
Winter12
37 | P a g e
ADM301 Exam Outline Details Dirty Data

Dirty data is any data within the system than is duplicated, incorrectly / erroneously entered, incomplete or outdated. It can use system resources and lead to poor reporting results.
Retrieving Data
There are several ways to retrieve data out of Salesforce: Reports Weekly Data Exports Data Loader and other API-based applications Community tools such as the Excel Connector The simpler the method the less flexibility
De-duplicating data
There are three necessary steps required to deal with de-duplicating data. 1. Establish what qualifies as a duplicate: Get this criteria from the data expert. 2. Find a common identifier between duplicates. 3. Determine additional duplicate field info and method for de-duping. Once you have carried out the necessary steps the data should be scrubbed to remove formatting and the field data should be concatenated. AppExchange: DemandTools is a .NET client applications developed by CRMfusion Inc. it is a suite of tools for data maintenance, cleansing, discovery, and address verification. AppExchange: RingLead Declone is a tool which can identify duplicate leads, contacts, and accounts; it provides services for de-duplicating and reports from the tool can be linked to existing merge utilities in Salesforce. De-duplicating: Merging Using the Wizard The merge wizard merges duplicate accounts and can merge up to three accounts at a time. In order to use the merge wizard, the user must have the delete permission on their profile. Following the merger any non-surviving records are moved to the recycle bin. Entering Clean Data: There are a number of ways to minimize the entry of dirty data in your system: Users should be trained on established naming conventions Validation rules should be created to ensure that data is complete and obeys business rules before saving. Data quality standard can be enforced by using lookup fields, custom formula fields, and workflow field updates. Record types and page layouts can be modified to only display relevant fields and buttons. Visualforce can be implemented to manage data modifications. Cees van der Sluis Winter12 38 | P a g e

Apex can be implemented to prevent duplicate entries. The admin can download the Data Quality Dashboards to monitor their data.
Validation Rules: Implement Validation Rules to validate data can prevent bad data from entering the system. (Validation rules do not scrub or modify existing bad data). Using data validation the admin can enforce business rules to ensure: Properly formatted data Correct data types Date Ranges Data Entry Rules should be tested before deployment to ensure that they do not contradict with other rules or existing business logic. Custom Lookup Fields: Custom lookup fields are used in situations when picklists are too limiting, need to be used in multiple places, or need to be added to very frequently. In these cases, a custom lookup object can be used to create an enumerated list of common data to share across multiple objects. Lookup Filters: Lookup filters are administrator settings that restrict the values and lookup dialog results for a field. The administrate settings on: Lookup Fields Master-Detail Fields Hierarchical relationship fields Record Types & Page Layouts: Record types allow the administrator to offer different business processes, picklist values, and page layouts to users based on their profiles. Page Layouts allow the administrator to define page layouts for objects and ensure that only relevant fields, picklist values and buttons that apply to the business scenario make sense.
Page layouts are driven by record types which are enable for the appropriate profile. Button Overrides and Visualforce: It is possible to override the action of a standard button on a record page to augment standard Salesforce behaviour. The action performed by the override is determined by a Visualforce page - usually in conjunction with a Visualforce controller (Apex code)
Cees van der Sluis
Winter12
39 | P a g e

Data Quality Analysis Dashboards: Reporting mechanisms in Salesforce are the best way to identify dirty data. The AppExchange provided for dashboards and related reports under the term Data Quality Analysis Dashboards. These dashboards contain components related to data quality and use Data Quality Scores (a weighted system that assigns values to fields that contain key data) Account Owner Report: It can be hard to control the introduction of duplicate records in a private sharing model. The Account Owner Report can help with this; it lists all account records and their owners in a private account sharing model. This report needs to be enabled by the administrator.
Cees van der Sluis
Winter12
40 | P a g e
Analytics & Reporting

Best Practices for Managing Storage Usage:
Monitor data usage to be able to handle storage shortages before they happen. Archive older data so that it can be removed from Salesforce. Mass delete records after archiving. Store data locally and provide links in Salesforce. Purchase additional storage in blocks of 50mb and 500mb.
AppExchange: Document Tab Management Dashboard. This dashboard from the AppExchange can be used to monitor the documents tab capacity and track by file type, file size, folder name and document author.
Mass Delete:
The Mass delete records functionality is within the Salesforce Application and allows the user to delete up to 250 records at a time. It is limited to use with Accounts, Leads, Activities, Contacts, Cases, Solutions and Products. Records can also be deleted using API based solutions such as the Force.com Data Loader. Actions that cause Irreversible changes to data in Salesforce: Changing Field Data Type Using Import Wizard Mass Transfer of Records Mass Delete of Records Mass Reassign of Account Teams Mass Reassign of Opportunity Teams Mass Update of Addresses Performing an Update via the API Performing a Mass Delete via the API Methods for Backing Up Data in Salesforce: The Weekly Data Export Service Exporting Reports Extracting Object Data with the Data Loader Leveraging Data Replication capabilities of API o getUpdated retrieves a list of individual objects that have been updated o getDeleted retrieves a list of individual objects that have been deleted
Adoption Dashboards
There are three Adoption Dashboards, and their associated reports available on the AppExchange. Downloading this app will create an "Adoption Dashboards - AppExchange" Dashboard folder along with a Reports folder called "Dashboard Reports - Adoption."
Cees van der Sluis
Winter12
41 | P a g e

The available Adoption Dashboards are: Usage (who's in and what are they doing?) Data Quality (can we trust what we see?) Business Performance (are we succeeding?) The Salesforce Adoption Dashboards provide visibility to relevant user login history & trending, adoption of key features such as accounts & opportunities, and critical sales and marketing productivity enhancers. Relevant user login history and trending
Cees van der Sluis
Winter12
42 | P a g e

Adoption of key Salesforce.com features
Adoption of critical sales and marketing productivity enhancer
Cees van der Sluis
Winter12
43 | P a g e
Force.com Code (Apex)

Apex Code Overview
Apex is a procedural scripting language that is written in discrete pieces and is executed by Force.com. It uses syntax like Java and acts like a stored database procedure. Apex runs natively on Salesforce servers which makes it more powerful and faster than non-server code such as Javascript and Ajax. Using Apex developers can add business logic to system events, this includes button clicks, related record updates and data loads. Apex enables developers to add business logic to most system events, including button clicks, related record updates, and Visualforce pages. Apex code can be initiated by Web service requests and from triggers on objects. Apex can be stored on the platform in two different forms: A class is a template or blueprint from which Apex objects are created. Classes consist of other classes, user-defined methods, variables, exception types, and static initialization code under Your Name | Setup | Develop | Apex Classes. A trigger is Apex code that executes before or after specific data manipulation language (DML) events occur, such as before object records are inserted into the database, or after records have been deleted. Triggers are stored as metadata in Salesforce. A list of all triggers in your organization is located at Your Name | Setup | Develop | Apex Triggers. Apex generally runs in system context; that is, the current user's permissions, field-level security, and sharing rules arent taken into account during code execution. You must have at least 75% of your Apex covered by unit tests before you can deploy your code to production environments. In addition, all triggers must have some test coverage. See About Apex Unit Tests. After creating your classes and triggers, as well as your tests, replay the execution using the Developer Console. Apex Support Apex support is provided through extensive documentation, an Eclipse IDE plugin tool, a variety of available deployment tools that allow code to be migrated between orgs and the mandatory creation of test scripts that can be run in a developer environment / the UI / or by Salesforce support personnel. Multi-Tenant Data and Code Just as multi-tenant data requires precautions to maintain privacy and scalability, multi tenant code requires governing limits to ensure security and efficiency.
Cees van der Sluis
Winter12
44 | P a g e
ADM301 Exam Outline Details When to use Apex

When you want to attach business logic to a data event (insert, update, delete) When you want this logic to execute regardless of the origin of the event When you want to process multiple records at the same time When you want to use classes that will be used by other developers.
When not to use Apex (Use the Web Services API Instead)
When you want to augment Salesforce behaviour without investing in Apex. When you want to add functionality to an S-Control or composite app to process one record at a time. When you want to integrate with a third party system.
Apex use cases

In the following cases you should make use of Apex: Field updates on other records Data driven sharing Multi step wizard Callout to external Web service Custom Web service Automate record creation/deletion Cleanse / repair existing records Custom Email handler Custom button action Custom report page
Dynamic Approval Routing leveraging Apex

Have a situation in which you need to dynamically choose an approver based on business rules? Need an example in which you leverage Apex code to choose the right approver at runtime depending on criteria in a record? Use the Spring '08 Dynamic Approval Routing. A sample is available in which a dynamic approval process is used for opportunity discounts. The approvers are based on the opportunity owners region and the account type associated with the opportunity. The process routes opportunity records through three levels of approval. Get it from the AppExchange: http://www.salesforce.com/appexchange/detail_overview.jsp?id=a0330000005AIHmAAO The sample solution uses Apex to determine the authorized approvers stored in a custom object, and shows how the new Approvals engine feature -Route to Related Users feature is leveraged to build truly dynamic approval routing capabilities. It also provides with a very good example of writing Apex code the correct way making sure every line of code is designed for bulk operation as well as a suite of tests which results in a code coverage of 100%.
Cees van der Sluis
Winter12
45 | P a g e
ADM301 Exam Outline Details How to access IDE Tools and Apps
IDE Tools can be downloaded / accessed via the menu: Your Name | Setup | Develop | Tools Apps can be downloaded from the App via the menu: Your Name | Setup | Deploy | AppExchange Marketplace
Cees van der Sluis
Winter12
46 | P a g e
Force.com Pages (Visualforce)

Force.com Pages
Introduction Visualforce uses a tag-based markup language to give developers a more powerful way to build applications and customize the Salesforce user interface. With Visualforce you can: Create custom user interfaces that easily leverage standard Salesforce styles Create custom user interfaces that completely replace the standard Salesforce styles Build wizards and other navigation patterns that use data-specific rules for optimal, efficient application interaction Visualforce comes with a rich component library that allows you to quickly build pages without having to create a lot of functionality yourself. In the Visualforce markup language, each tag corresponds to a coarse or fine-grained component, such as a section of a page, a related list, or a field. The components can either be controlled by the same logic that is used in standard Salesforce pages, or developers can associate their own logic with a custom controller or controller extension written in Apex. Visualforce allows developers to replace standard page layouts with completely custom pages for any application, user interface, or device; it uses Apex for business logic functionality. Additionally, Visualforce offers a user-friendly, split-screen development environment. Once Save is clicked, the code is immediately tested. The editor also offers limited syntax highlighting as well as online documentation. There are two types of Force.com user interface technologies Page Builder & Visualforce. With Page Builder: The UI is generated automatically. There is limited or no control of UI behaviour. There is limited control over the look and feel (All UIs are consistent).
With Visualforce: The UI is generated by the developer. There is full control of the UI behaviour. There is full pixel level control over the UI.
Cees van der Sluis
Winter12
47 | P a g e
ADM301 Exam Outline Details Visualforce key features

Pages: Design definition of an apps user interface Implemented using standard web technologies including HTML and JavaScript Dynamically dtects devices and associate with specific design definitions Components: Reuse standard Salesforce and custom designed UI components Over 50 standard Salesforce UI elements available at GA Referenced via a tag library model Controllers: Ability to reuse any standard Salesforce UI behaviour like new, edit save, etc (standard controller) and have access to Salesforce data Ability to define new UI behaviours and navigation using Apex (custom controller)
Visualforce Controllers
A Visualforce controller is a set of instructions that specify what happens when a user interacts with the components specified in associated Visualforce markup, such as when a user clicks a button or link. Controllers also provide access to the data that should be displayed in a page, and can modify component behavior. A developer can either use a standard controller provided by the Force.com platform, or add custom controller logic with a class written in Apex: A standard controller consists of the same functionality and logic that is used for a standard Salesforce page. For example, if you use the standard Accounts controller, clicking a Save button in a Visualforce page results in the same behavior as clicking Save on a standard Account edit page. If you use a standard controller on a page and the user doesn't have access to the object, the page will display a insufficient privileges error message. You can avoid this by checking the user's accessibility for an object and displaying components appropriately. A standard list controller enables you to create Visualforce pages that can display or act on a set of records. Examples of existing Salesforce pages that work with a set of records include list pages, related lists, and mass action pages. A custom controller is a class written in Apex that implements all of a page's logic, without leveraging a standard controller. If you use a custom controller, you can define new navigation elements or behaviors, but you must also reimplement any functionality that was already provided in a standard controller. Like other Apex classes, custom controllers execute entirely in system mode, in which the object and field-level permissions of the current user are ignored. You can specify whether a user can execute methods in a custom controller based on the user's profile. A controller extension is a class written in Apex that adds to or overrides behavior in a standard or custom controller. Extensions allow you to leverage the functionality of another controller while adding your own custom logic. Cees van der Sluis Winter12 48 | P a g e

Because standard controllers execute in user mode, in which the permissions, field-level security, and sharing rules of the current user are enforced, extending a standard controller allows you to build a Visualforce page that respects user permissions. Although the extension class executes in system mode, the standard controller executes in user mode. As with custom controllers, you can specify whether a user can execute methods in a controller extension based on the user's profile.
Where Can Visualforce Pages Be Used?

Developers can use Visualforce pages to: Override standard buttons, such as the New button for accounts, or the Save button for contacts Override tab overview pages, such as the Accounts tab home page Define custom tabs Embed components in detail page layouts Create dashboard components or custom help pages Customize, extend, or integrate the sidebars in the Service Cloud console (custom console components)
Cees van der Sluis
Winter12
49 | P a g e
Integrations
Salesforce - Web Services API
Introduction Web services are a set of related application functions that can be invoked from the internet. (Invocations are in the form of XML requests and responses between client and server) Clients and Servers can be implemented in different environments. The API is used in the following examples: Salesforce Data Loader Connect for Microsoft Outlook Connect for Microsoft Office Offline Edition Most Commonly Used API Calls: Query Executes against the specified object (SOQL) Retrieve Retrieves one or more objects based on the specified IDs Create Adds one or more records to an organizations data Update Updates one or more existing records Upsert Creates or updates an object based on a match of an ExternalID field Delete Deletes one or more individual objects Undelete Undeletes eligible records from the Salesforce recycle bin Metadata API The Metadata API allows for asynchronous creation, update, and deletion of custom objects and fields. Metadata tools on the AppExchange Marketplace can help you to take advantage of this powerful capability.
Web Controls & External Web App Integrations

A web application runs on a customer hosted web server. It has a custom UI and is generally written in ASP.NET or JSP. The web application uses the Force.com API to modify Salesforce data. It is primarily used for highly customized UI or Business Logic functionality. Methods that Website Integration can be used to present information on a public facing website Web to Case Case Web form input Web to Lead Lead Web form input Self Service Portal Present Case data back to a customer Customer Portal Present case and custom object data back to the customer
Cees van der Sluis
Winter12
50 | P a g e

X To Web Used when additional flexibility is required over the standard website integration allows Salesforce data to be published on a website using a pre-determined SOQL statement of the websites front end. DescribeObject metadata calls are used to ensure that picklist values on the website match those in Salesforce. Salesforce Username and Password are stored in the web controls configuration file to ensure seamless integration.
Web to X Web To X can be used to drive data entry into Salesforce avoiding the need to re-key information. Salesforce Username and Password are stored in the web controls configuration file to ensure seamless integration. Force.com Sites Force.com sites are public and authenticated websites or portals that are built with various Visualforce pages from data and content in the Salesforce application. These sites can be accessed from branded domain names.
Increasing User Adoption

There are two outlined steps for measuring user adoption in a company: Define what adoption means to the company and create measurement tools around the definition. Determine the metrics that will be used to measure adoption and design relevant dashboard to measure Using Salesforce Applications to increase adoption There a number of Salesforce applications that can be leveraged to increase used adoption: Send Newsletters through Marketing Campaigns to target Salesforce users or the entire company. These newsletters can consist of tips and tricks, training opportunities, and login and adoption statistics. Use Salesforce Call Centre to track issues requiring administrator attention. Create Portals or Integrations for non Salesforce users to access Salesforce data. Identify external processes for custom object tracking (such as AppExchange Applications). Fostering Executive Sponsorship Having executive sponsorship is a great way to ensure that your users are motivated to continue their use of Salesforce. Executives can be motivated using the following methods: Updating the Salesforce home page with a revolving message from a high-level executive. Encouraging company leaders to use and mention Salesforce in meetings.
Cees van der Sluis
Winter12
51 | P a g e

Ask executives to lead by example in Salesforce usage through Data Entry & Dashboard Monitoring.
Winning Over Sales In order to win over adoption from the sales department there are a number of simple areas that can be configured: Make simple information tracking easy. Automate advanced processes. Send the right message (If its not Salesforce it doesnt exist!). Soliciting Feedback There are a number of methods available for soliciting feedback from your users in order to update the system and maintain user adoption: Send surveys to understand system usage. Create a user group or inter-department committee to evaluate feedback. Conduct face-to-face interviews to understand future requirements. Leverage the Salesforce Community. Using Salesforce in Meetings In addition to improving user productivity, Salesforce can help share and display data quickly and efficiently. The user interface can also be customized to display data to the specific meeting audience. Some additional uses are: Project Salesforce data during the meeting. Review tasks and events in the app during the meeting. Help team members build views and reports for the meeting. Run exception reports to target missing information. Dashboards Dashboards can be used in meeting to display data from external systems side-by-side with Salesforce. A variety of dashboards are available for download from the AppExchange. Dashboard components can be managed to suit the needs of your target audience and dashboards can be cloned to suit the requirements of each meeting. Custom Links and URL Integrations You can use custom links and URL integrations to adapt the Salesfore UI to your users preferences. You can add useful links to the Salesfore sidebar and add parameters to the URL using Salesforce data at runtime.
Force.com Connect for Microsoft Office Overview

Force.com Connect for Microsoft Office integrates Microsoft Office with Salesforce. Connect for Office includes an Excel add-in and a Word add-in.
Cees van der Sluis
Winter12
52 | P a g e

Integration with Microsoft Excel The Excel add-in securely delivers your Salesforce reports into Excel in real time with a simple interface. You create the reports you need in Salesforce, then pull them into an Excel worksheet, and optionally use Excels formulas, charts, and pivot tables to customize and analyze your data. As a last step, you can distribute your customized Excel worksheets via the Documents tab, allowing all users to track customized analytics in real time. Integration with Microsoft Word The Word add-in helps you create mail merge templates for use with Salesforces online mail merge utility. The Word add-in allows you to quickly and easily insert Salesforce merge fields into a Word mail merge template.
Force.com Connect Offline Overview

With Force.com Connect Offline, you can work on your key deals anywhere, any timetotally unplugged. Connect Offline is a client application that lets you access a subset of Salesforce records using the same browser-based interface as the online system but without an Internet connection. Use Connect Offline to view, edit, create, and delete accounts, activities, contacts, opportunities, leads, and custom object records (including relationship groups). You can also add and update products and schedules on opportunities. The subset of Salesforce records accessible in Connect Offline is referred to as a briefcase. Administrators can create briefcase configurations, which are sets of parameters that determine the records available in the briefcases of users with a specific profile. Organizations can have multiple briefcase configurations and associate each with a different set of profiles to simultaneously suit the needs of various types of offline users. For example, one configuration might include leads and opportunities in the briefcases of users with a Sales Representative profile, while another configuration includes accounts and related opportunities in the briefcases of users with an Account Executive profile. Users without an assigned briefcase configuration can configure the settings for their own Connect Offline briefcase and can manually select the accounts the briefcase includes. When online, users can synchronize their Connect Offline briefcases with Salesforce. During synchronization, the changes to records in the briefcase are implemented in Salesforce, and viceversa. This ensures that both Salesforce and Connect Offline have the most current records. If updates to a record in the briefcase conflict with updates to a record in Salesforce, Connect Offline displays the conflict resolution tool, which allows users to easily resolve the conflict. Installing Connect Offline For organizations using Unlimited, Enterprise, and Developer Editions, salesforce.com provides one Connect Offline license for each Salesforce license. Organizations using Professional Edition must purchase Connect Offline licenses separately. Users without a Connect Offline license can use for a 30-day trial period.
Cees van der Sluis
Winter12
53 | P a g e

To allocate a Connect Offline license to a user within your organization, edit the user's record and select the Offline User checkbox. Users must have this checkbox selected to use Force.com Connect Offline. Installing an Individual Client Download and install the Connect Offline client Deploying Connect Offline System-Wide If your organization uses Windows, network administrators can install Connect Offline on several machines at once by using a downloadable zipped MSI package.
Cees van der Sluis
Winter12
54 | P a g e
Sandbox & Development as a Service

Development as a Service
Many of the Force.com components used to build an application are captured as metadata within the platform. An important use of Development as a Service (DaaS) is migrating metadata components from one organization to another. You cannot develop Apex in your Salesforce.com production organization. Live users accessing the system while you are developing can destabilize your data or corrupt your application. Instead, salesforce.com recommends that you do all your development work in either a sandbox or a Developer Edition organization. Resolution To deploy code from a Sandbox or Developer Edition org to Production, you will need to use either the Force.com Migration Tool or the Force.com IDE. Note: If you deploy to a production organization, 75% of your Apex scripts must be covered by unit tests, and all of those tests must complete successfully. While only 75% of your Apex code must be covered by tests, your focus shouldn't be on the percentage of code that is covered. Instead, you should make sure that every use case of your application is covered, including positive and negative cases, as well as bulk and single record. This should lead to 75% or more of your code being covered by unit tests. Force.com Migration Tool The Force.com Migration Tool is a Java/Ant-based command-line utility for moving metadata between a local directory and a Force.com organization. Force.com IDE The Force.com IDE is a powerful client application for creating, modifying and deploying Force.com applications. Based on the Eclipse platform, it provides a comfortable environment for programmers familiar with integrated development environments, allowing you to code, compile, test, package and deploy all from within the IDE itself. Much of the actual work, such as compilation, happens on the Force.com platformthe Force.com IDE performs the communication and result parsing transparently.
Force.com Sandbox
Salesforce gives you the ability to create multiple copies of your organization in separate environments for a variety of purposes, such as testing and training, without compromising the data and applications in your Salesforce production organization. These copies are called sandboxes and are nearly identical to your Salesforce production organization. For a list of differences, see Force.com Sandbox Setup Tips and Considerations.
Cees van der Sluis
Winter12
55 | P a g e

Sandboxes are completely isolated from your Salesforce production organization, so operations you perform in your sandboxes do not affect your Salesforce production organization, and vice-versa. Types of sandboxes: Configuration Only Configuration-only sandboxes copy all of your production organization's reports, dashboards, price books, products, apps, and customizations under Your Name | Setup, but exclude all of your organization's standard and custom object records, documents, and attachments. Creating a configuration-only sandbox can decrease the time it takes to create or refresh a sandbox from several hours to just a few minutes, but it can only include up to 500 MB of data. You can refresh a configuration-only sandbox once per day. Developer Sandbox Developer sandboxes are special configuration-only sandboxes intended for coding and testing by a single developer. They provide an environment in which changes under active development can be isolated until they are ready to be shared. Just like configuration-only sandboxes, developer sandboxes copy all application and configuration information to the sandbox. Developer sandboxes are limited to 10 MB of test or sample data, which is enough for many development and testing tasks. You can refresh a developer sandbox once per day. Full Full sandboxes copy your entire production organization and all of its data, including standard and custom object records, documents, and attachments. You can refresh a fullcopy sandbox every 29 days.
Create new Sandbox

To create sandboxes follow these directions: Login to Salesforce.com Click on Setup | Administration Setup | Data Management | Sandbox Click the button New Sandbox Give the sandbox a name, a description, and the type. Click the button Start Copy. If you do not see Sandbox under Data Management then your company may not have purchased any sandboxes and you will need to contact your sales representative. Sandbox Limits The following limits apply to sandboxes: You can refresh a full copy sandbox 29 days from its previous refresh or creation. If you delete a full-copy sandbox, you must wait 29 days to replace it. You can refresh a configuration-only sandbox (including developer sandbox) once per day. You may order up to a maximum of three full sandboxes. You may order up to a maximum of six configuration-only sandboxes. Cees van der Sluis Winter12 56 | P a g e

Enterprise Edition includes one developer sandbox. Unlimited Edition includes one full sandbox with the option to purchase up to three more full sandboxes.
Force.com Sandbox Setup Tips and Considerations

When you setup a Sandbox you need to take the following into consideration: Servers and Ids Username and Email Address Modification o Usernames should always be unique Creating, Refreshing, and Deleting Sandboxes o Long Process o Limited number of Sandbox environments available Accessing Sandboxes Sandbox Storage Limits Customization and Data Changes Service Exclusions o Case escalation o Opportunity reminders o Contract expiration warnings o Subscription summary o Data exports o The ability to create Salesforce sandboxes. o Case escalation, opportunity reminders, and contract expiration warnings are disabled because they automatically send email to contacts, customers and users who should not interact with sandboxes. o Testing Salesforce for Google AdWords in your sandbox is not supported. o Email service addresses that you create in your sandbox cannot be copied to your production organization. Other Service Differences
Cees van der Sluis
Winter12
57 | P a g e

ADM301 Certification Topics

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ADM301 Certification Topics

Uploaded by

Copyright:

Available Formats

ADM301 Exam Outline Details

ADM301 Exam Outline Details

Cees van der Sluis

ADM301 Exam Outline Details

Software as a Service (SaaS)

Cees van der Sluis

ADM301 Exam Outline Details

Cees van der Sluis

ADM301 Exam Outline Details

Cees van der Sluis

ADM301 Exam Outline Details

New Release Information

Cees van der Sluis

ADM301 Exam Outline Details Answers Overview:

Cees van der Sluis

ADM301 Exam Outline Details

CRM Content Overview:

ADM301 Exam Outline Details

Cees van der Sluis

ADM301 Exam Outline Details

ADM301 Exam Outline Details

Cees van der Sluis

ADM301 Exam Outline Details

Force.com (Platform as a Service)

The Cloud computing model

Cees van der Sluis

ADM301 Exam Outline Details Types of Applications suitable for Force.com

Cees van der Sluis

ADM301 Exam Outline Details

Cees van der Sluis

ADM301 Exam Outline Details

Cees van der Sluis

ADM301 Exam Outline Details

Cees van der Sluis

ADM301 Exam Outline Details Formula Overview:

Categorizing data with formulas IF(....IF(...)IF(...)) or CASE(...)

Cees van der Sluis

ADM301 Exam Outline Details

Custom Buttons and Links

Cees van der Sluis

ADM301 Exam Outline Details

Description Display Type

Cees van der Sluis

ADM301 Exam Outline Details

Usage of Custom Buttons

Button Overrides and Visualforce

Cees van der Sluis

ADM301 Exam Outline Details

Security and Access

Cees van der Sluis

ADM301 Exam Outline Details

Cees van der Sluis

ADM301 Exam Outline Details

What are the salesforce.com audit levels?

ADM301 Exam Outline Details

Cees van der Sluis

Territory Management Overview:

Cees van der Sluis

ADM301 Exam Outline Details

Cees van der Sluis

ADM301 Exam Outline Details

Record Types versus Page Layouts

Page Layout Assignment