Platform Fundamentals

登録は簡単!. 無料です
または 登録 あなたのEメールアドレスで登録 Platform Fundamentals により Mind Map: Platform Fundamentals

1. author: Hans Pan

1.1. updated on 7/23/2012

2. 1. introduction

2.1. the technologies behind

2.1.1. multitenant architecture `latest patches and functionalities no worry on update / upgrade

2.1.2. metadata-driven development model metadata in DB not hard coded higher productivity

2.1.3. web service API

2.1.4. Apex

2.1.5. Visualforce

2.1.6. salesforce mobile

2.1.7. sites share apps installed on salesforce to users out of salesforce no username and password needed

3. 2. about recruiting app

3.1. technologies offered by platform

3.1.1. custom objects

3.1.2. security and sharing rules

3.1.3. workflow and approval process

3.1.4. custom reports and dashboards

3.1.5. visualforce

4. 3. reviewing database concept

4.1. an object in is more than a table

4.1.1. built-in user interface

4.1.2. security and sharing model applied

4.1.3. workflow and approval process activated and supported directly

4.1.4. reports supported directly

4.2. terms

4.2.1. object standard object custom object

4.2.2. field standard field custom field

4.2.3. data value

5. 4. building a simple app

5.1. an app

5.1.1. name

5.1.2. logo

5.1.3. set of tabs

5.1.4. default landing tab

5.1.5. profile assignments {profile : is visible, is default}

5.2. in iterative way

5.3. an object

5.3.1. name lable name object name

5.3.2. record name field data type

5.3.3. optional features allow reports allow activities track field history

5.3.4. deployment status

5.4. a tab

5.4.1. for an object

5.4.2. color scheme and icon

5.4.3. profile assignments {profile : option} default on default off tab hidden

5.4.4. app assignments {app : is accessible

5.5. a field

5.5.1. data type text type text text (encrypted) text area text area (long) text area (rich) currency type checkbox type date type build-in popup calendar dialog

5.5.2. field lable name

5.5.3. field name

5.5.4. field security setting on various profiles {profile : is visible, is readonly}

5.5.5. layout field setting

6. 5. enhancing with advanced fields

6.1. advanced fields

6.1.1. picklist type standard picklist multi-select picklist

6.1.2. field dependency controlling field dependent field

6.1.3. custom formula field

6.1.4. dynamic default field value

6.2. validation rules

6.2.1. rule name

6.2.2. error condition

6.2.3. error message

6.2.4. where to display error message

6.3. page layout

6.3.1. section section name layout one column two columns tab-key order display section header on

6.3.2. field properties required field readonly field

7. 6. extending using relationships

7.1. a relationship custom field

7.1.1. a many-to-one relationship on referring and referred

7.1.2. put the relationship field onto the object which is one side on the many-to-one relationship

7.1.3. types lookup relationship field simplest most flexible optional how impact implementation master-detail relationship field how impact when to use implementation

7.1.4. examples lookup hiring manager relationship from position to user job application between position and candidate master-detail review on job application

7.2. many-to-many relationship

7.2.1. junction object two master-detail relationships first master-detail relationship will be primary junction object uses color scheme and icon of primary master ownership and sharing rules of junction object is determined by primary master in secondary master-detail relationship, detail objects are deleted as well once the master object is deleted.

7.3. data import

7.4. extra fields

7.4.1. external ID field indexable searchable used for importing data

7.4.2. text field length is required is unique is case sensitive is external ID default value

7.4.3. email field is required is unique is external ID

7.4.4. number field length (left of decimal point) decimal place (right of decimal point)

7.4.5. checkbox field default: is checked

7.4.6. phone field

7.4.7. rollup summary field

7.4.8. formula field cross-object formula

7.5. search layout

7.5.1. search results

7.5.2. lookup dialogs

7.5.3. tab related list pay layout is determined by both parent object's related list properties (first) and child object's tab layout setting

7.5.4. search filter fields

8. references

8.1. functions in formula

8.1.1. TODAY()

8.1.2. HYPERLINK()

8.1.3. IFBLANK()

8.1.4. IFNULL()

9. 8. Collaborating with chatter

9.1. setting

9.1.1. enable

9.1.2. email notification

9.1.3. approval posts

9.1.4. coworker inviation

9.1.5. customer inviation

9.2. field tracking

9.2.1. {object : field}

10. 9.Using custom workflow and approval processes

10.1. workflow

10.1.1. workflow rule implementation related to an object give rule name define when evaluating define rule criteria

10.1.2. workflow action what we can do? task field update alert outbound message when they can be done? immediately time dependent

10.1.3. associated with a single object

10.2. queue

10.2.1. impelementation queue email supported objects queue members by individual users by roles by roles and subordinates by group

10.3. email template

10.3.1. types text html custom visualforce

10.4. approval process

10.4.1. apply approval process to all records or certain records matching criteria

10.4.2. concepts initial submission record locking automatical approval final approval final reject actions associated with iniitial submission, approval / rejection, final approval / rejection. approval step (has) approver(s) filter criteria approval action rejection action recall action approval action not associated with approval step action associated with approval step same types as workflow action once approval process is activated, approval steps cannot be edited even process deactivated

10.4.3. best practice notify approver through email once submission

10.4.4. implementation target object who can edit once it is locked administrator only administrator or assigned approver 2 ways to config jump star standard next automated approver determined by manager record owner's manager record submitter's manager approver page layout only can be configured / provided in approval process configuration process fields displayed on the page layout security setting from where approver can access approval page? who can submit adding approval history related list to the target object all pay layout allow submitter to recall approval steps step number step name step record filter criteria select approver allow approver's delegate to handle

10.4.5. process visualizer

11. 10. Analyzing data with reports and dashboards

11.1. the need of company managers and executive staff

11.2. report

11.2.1. is composed of table of data columns records records filter one or multiple grouping graph

11.2.2. 3 formats tabular simplest no grouping no graph summary grouping row of data subtotal view charts when used matrix grouped by both row and column graphs when used

11.3. report tab

11.4. report folder

11.5. dashboard

11.5.1. show data from source reports as visual components

11.5.2. every dashboard has a running user which data is displayed in the dashboard access to the details depend on viewer's security setting

11.5.3. dynamic dashboard

11.5.4. 5 varieties charts bar column line pie donut funnel tables metrics gauges visualforce pages

11.5.5. schedule a dashboard freshing

11.6. custom report type

11.6.1. primary object

11.6.2. related objects

11.6.3. relationship between primary and related

11.6.4. page layout

11.7. create a report

11.7.1. select a report type

11.7.2. select report format

11.7.3. define filters standard filters by owner by date custom filters field filter

11.7.4. adding charts

11.7.5. varies create a summary report select grouping field(s)

12. 11. Moving beyond point-and-click app development

12.1. mash-up

12.1.1. web service

12.1.2. visualforce

12.2. visualforce pages

12.2.1. controller the style of the page

12.3. mass update

12.4. custom buttons

12.4.1. detail page button

12.4.2. list button

12.5. sites

12.5.1. public access setting

13. 7. Security and sharing data

13.1. page layout setting

13.1.1. {object : page layout}

13.1.2. standard and custom objects

13.2. data administration

13.2.1. global data administration View All Data Modify All Data

13.2.2. app / object data administration View All (on object level) Modify All (on object level)

13.3. concepts

13.3.1. static 3 levels of access object level field level record level profile the following can be set through profile define profiles as per job function 6 standard profiles app setting tab setting user/function permissions field securities 2 ways to define record permission level 1 - org-wide defaults, most restricted definition level 2 - role hierarchy level 3 - sharing rules level 4 - manual sharing record type show ... to different users based on profiles

13.3.2. dynamic create a user-object access matrix

13.4. best practices

13.4.1. create new profiles from standard profiles, then edit

13.4.2. whether role hierarchy is used to grant access can be defined / changed / set on each object

13.4.3. cannot define sharing rules on the detail object in master-detail relationship

13.4.4. sharing access to a junction object record is determined by sharing access to both associated master records Sharing Setting option on the relationship field

13.5. how-to-do

13.5.1. 1. create profile (thru cloning)

13.5.2. 2. set app access thru profile {custom app : is visible} which custom app is default

13.5.3. 3. set tab access thru profile options default on default off tag hidden

13.5.4. 4. set object security thru profile {object : is able to C / R / U / D, is able to view / modify all} view all - be able to ready all records modify all - full access to all records

13.5.5. 5. set field-level security thru profile {object : field security setting} {field : is visible, is read-only}

13.5.6. 6. set org-wide defaults for record level security

13.5.7. 7. set role hierarchy create a role assign users to that role

13.5.8. 8. set sharing rules

13.5.9. 9. manually share records

13.5.10. 10. set record types select an object create a record type profile setting picklist value setting define different page layouts for different record types and assign them to different profiles

13.5.11. 11. delegating data administration 2 ways to do object-level permission delegated administration group

13.5.12. function permissions administrative permissions general user permissions {function : is checked / enabled}