DEV 401: Reporting

Relationship Implications on Reporting: Lookup relationship joins data from two related objects Master-Detail relationship joins data from three objects A primary or master object determines the visibility of records Reports can only display one child at a time For more information on Joined Reports: https://help.salesforce.com/apex/HTViewHelpDoc?id=reports_joined_format_concepts.htm&language=en_US For more information on Formulas in Report...

DEV 401: Data Management

Record Ownership: Owners have full access to their own records which is a single row of information if we were to compare to a spreadsheet. Child records in the master-detail relationship do not have an owner as ownership is inherited from the parent. In order to transfer a record to another user they must have at least Read access. Records can be owned by either a user or a queue. Record Access Levels: Read Only Read/Write Full Access: Allows for reading, editing, deleting, sharing or transferring For more information on Record Ownership: https://developer.salesforce.com/blogs/engineering/2013/10/behind-the-scenes-of-record-ownership-in-salesforce.html For more information on Organization Wide Defaults: https://help.salesforce.com/HTViewHelpDoc?id=security_sharing_owd_users.htm&language=en_US *Child records in a lookup relationship have independent organization wide defaults from their parents. Child records from a Master-Detail relationship inherit the organization wide default from their parents. For more information about Role Hierarchy: https://help.salesforce.com/apex/HTViewHelpDoc?id=admin_roles.htm   For more information on Public Groups: https://help.salesforce.com/apex/HTViewHelpDoc?id=user_groups.htm&language=en   For more information about Sharing Rules: https://help.salesforce.com/apex/HTViewHelpDoc?id=security_about_sharing_rules.htm&language=en_US Manual Sharing: Is used to grant access on a one off basis and can be granted by the record owner or anyone above the owner in the role hierarchy or the system administrator. Apex Sharing: Users with the “Modify All Data” permission can create an Apex Sharing Reasons. For more information on Apex Sharing...

DEV 401: Business Logic

Custom Formula Fields: Used to build business specific calculations using simple wizards and formulas. Can reference: Standard Custom Other Formula Fields Fields on Related Objects Cross Object Formulas: Can be created for objects linked by either Master-Detail or Lookup relationships. Can contain objects that span across multiple levels of relationships. Limit for cross-object formulas is 10. Cannot reference Cross Object Formulas in roll-up summary fields or merge fields for objects related to activities. Roll-Up Summary Fields: Used to calculate values from a set of records that have been related. Read-only formula fields that can display the sum, minimum, maximum or record count. Can be used in some standard relationships and all custom master-detail relationships. Can be made to automatically display a value on a master record based on the values of the detail records. You can also include all records in the roll up or just those that meet certain...

DEV 401: User Interface

Available Customization: Custom Logo - Can be GIF or JPG should be less than 20KB Custom Landing Page - Any tab can be selected as a Default Landing Tab Custom Tabs: Custom Object Tab: can be used to display the data of any custom object Web Tabs: display external Web-based application or Web page Visualforce Tab: display a Visualforce page Page level customization: Fields: order of appearance Custom links: order of appearance Field locations Page section customization Field properties - you can set them as visible, read only, and required To control the different settings of the page layout use the Enhanced Page Layout. To add a Chatter feed to a page layout navigate to Feed Tracking in the setup. Salesforce1: Mobile app, can access from Play Store, App Store or mobile browser. Supports declarative customization including: custom objects custom fields page layouts Quick Actions: Allows you to add actions to the Chatter publisher. Types: Create Actions - Create records, respects validation rules and required field settings Log a Call - saved as a completed task Update Actions - allows users to update records from the record page Custom Actions - require Visualforce pages, should be used when you need beyond standard page layout editor or record page Can be Object specific or Global Global Publisher Layouts: Control which actions, only global actions can be displayed, multiple global layouts can be created and assigned to different profiles. For more information on Global Publisher Layouts: https://help.salesforce.com/HTViewHelpDoc?id=working_with_global_publisher_layouts.htm&language=en_US...

DEV 401: Data Model

When looking at the Data Model it is important to understand what Salesforce considers to be an Object. Object: An object is analogous to a table that contains the data. However, it is important to understand an Object is more abstract that just a database table. Records: These are analogous to a row in the database. A record is a single instance of a Salesforce object and consists of information for more than one field. Field: A field is analogous to a column in the database and stores a piece of information.   Things you can do with Objects: Configure access control features Create relationships to associate Objects with each other Report on the Object Search the Object Some of the Standard Objects are: Account Opportunities Contact Event Leads In addition to Standard Objects you can create Objects known as Custom Objects. A user interface is created when a custom objected is created. A custom object contains certain standard fields upon creation but also allows you to do the following: Create custom fields Create relationships to other objects Create page layouts There are two field types in Salesforce: Standard and Custom A standard field is one that has been generated by the system and allows for minimal modification, a custom field has been user created. For each custom field there are multiple properties that can be specified: Label: This identifies the field name in the user interface. Name: This is the programmatic name assigned by the system and for a custom field the system will append a “_c” to the end of it Required: Specify whether or not a value must have been entered...

DEV 401: Overview of the Force.com Platform

What are the benefits of the Force.com platform, and what is its relationship to cloud computing? It enables you to configure and customize the Sales Cloud, Service Cloud, and Chatter. It provides point-and-click interface for many customizations. It includes workflow and logic, analytics, has Chatter built in, is mobile ready and has open APIs to connect to other applications. The multi-tenant architecture of the cloud computing model makes it possible for applications from different organizations to run on a common technology infrastructure. This multi-tenant architecture allows users to utilize a shared functionality. The analogy often used is that of an office building with shared services. Once inside the building services like security, electricity, maintenance, and storage space are already set up allowing you to plug in and start immediately. In a software situations this allows you to focus more on customizing the application instead of setting up a bunch of hardware, software and the operations required to run them. What development tools does the platform offer? It includes workflow and logic, analytics, has Chatter built in, is mobile ready and has open APIs to connect to other applications. Force.com is implemented through meta data. Put simply meta data is data about data. This meta data is used to explain, describe, locate or manage information. The most basic metadata is often associated with documents and includes the informational properties like the author, date created, date modified and file size. With multi-tenancy users experience automatic upgrades and don’t need to worry about buying and installing anything new. Salesforce has three product releases per year and ensures backward compatibility for the API and...