SalesForce Administrators Quick Notes - Administrator

1. App launcher: Take you to the apps that have been configured for your system. Apps are the applications that you have access to, for example, Sales, Service, Marketing, Community, etc.

2. Tabs: Used for primary navigation, similar to tabs on a workbook.  There are primary tabs and secondary tabs also used for navigation.  

3. Page Layout: This is how the page is set up in Salesforce.

4. Default Layouts: Contains data laid out in a specific way. They give you access to related lists, details, and news. Related lists our contact points of other data related to one specific piece of data.

5. Master data detail / parent child relationship: In a master data detail or parent child relationship if you delete an account, all contacts, cases, and opportunities will also be deleted.

6. Lookup relationship: In a lookup relationship a one-to-many relationship with multiple objects exists. For example, if you delete a lead associated with a campaign, the campaign object remains unaffected. Similarly, if you delete a campaign any leads associated with the campaign are unaffected.

7. Setup: The setup area is strictly for administrators. Most of the work that administrators perform will be completed in the setup area.

8. Object manager: This is a centralized location for managing objects.

9. Schema builder: Gives administrators the ability to look at database objects and look at relationships between objects for the entire organization.

10. Global search: Gives you the ability to search for data in the entire org.

11. Guidance center: You can use this area to provide training material for your users.

12. List views: Can be either standard or customized. There are three types: table, Kanban, split view.

13. Table view: Allows you to edit a record individually or in mass.

14. Kanban: Turns records into editable individual views.

15. Split view: Allows you to view records on the left and update records on the right.

16. Object: Table of data that can be either standard or custom. Objects can be related to each other.

17. Sandboxes: Copies of your Production org or another Sandbox. Sandboxes are used for development and testing purposes. configuration updates or development can be migrated to Production once testing is complete. Sandboxes exist so you do not negatively impact your Production, live client facing system. There are four types: Developer, Developer pro, Partial copy,  and Full copy.

18. Metadata: Includes configuration changes, custom objects custom fields page layouts and everything it entails.

19. Developer: Used for development and testing. It includes a copy of your Production org  or another Sandbox’s  metadata,  up to 200 megabytes. Used to  test configurations that do not require actual data.

20. Developer Pro: Used for development and testing. It includes a copy of your Production org or another Sandbox’s  metadata, up to 1 GB. It works for larger datasets than Developer Sandbox.

21. Partial copy: Used for User Acceptance Testing (UAT),  Quality Assurance Testing (QA), Integration Testing, or Training. It includes a copy of Production org metadata and sample of data up to 5 gigabytes.

22. Full copy: Used for testing. Includes a copy of Production org metadata and actual data. It  is the same size as your Production org. Generally used for performance testing, load testing, and staging before migrating to Production.

23. Using Sandboxes is considered best practice  to avoid  negatively impacting  your Production org. Things an  administrator should consider when testing in a Sandbox.

a. What Sandbox are you evaluating in?

b. What tests do you have in place to evaluate your build?

c. How will you perform user acceptance testing?