▪ While creating the object, we can enable ‘Track Field History’.

▪ If, we enable ‘Track Field History’ user can see ‘Set History Tracking’ button under ‘Custom Fields & Relationships’ section which is available on the object detail page.

▪ By clicking on ‘Set History Tracking’ button, we can enable tracking for the fields which ever we want.

▪ To see the object history, go to object’s record layout and add Object Name History related list to the layout.

▪ Whenever, user changes field value from one value to another value, it will show the history of the field in ‘Object History’ related list.

▪To create the Activities, while creating the object, we should check for ‘Allow Activities’ check box then user can add open Activities and Activity History related lists on the Object layout.

▪There are two types of activities

1. Task: Task is nothing but work assigned to a particular person, it doesn’t have certain time limit.
2. Event: It has certain time limit in that time only all persons should assemble after the time limit over, event will get complete.

▪ Once event or task status changed to ‘Completed’ then we can see those records under Activity History Related List.

▪ Tab name will be decided based on the Plural Label of the custom object, to rename go to corresponding object detail page and rename the plural label.

▪ Click on the Tab (Which should be related to any of the custom/standard object) > Expand Force.com Quick Access Menu > Edit Columns > Move the needed fields from Available Fields to Selected Fields. > Click on Save > User should be able to see multiple columns.

(OR)

▪ Click on Setup > Create > Objects > Select the corresponding object link > Under Search Layouts section > Click Edit which should be left to Object Tab > Move the needed fields from Available Fields to Selected Fields. > Click on Save > User should be able to see multiple columns.

▪ ISNULL() : works only for number data type fields, if we don’t populate with value for number fields it will return true.

▪ ISNULL() : won’t support TEXT data type fields because text fields never become null.

▪ ISBLANK() : supports both number as well as text data types.

▪ In some scenario’s, we should be able to control one of the fields (Dependent field) from another field (Controlling field), example If we select Country (Controlling field) as US then City (Dependent Field) should display only US cities.

• We can use checkbox data type fields also while creating dependent picklist (Note: Checkbox should be always controlling field)
• We can use multi-select data type fields also while creating dependent picklist (Note: multi-select data type field should be always dependent field)

▪ MVC Architecture – Model, View, Controller

▪ View – It is the user interface (Apps, Tabs, Page Layouts, Fields and Record Types)

▪ Controller – Business Logic (Save, Edit, New, Cancel and Delete – upon click on these button salesforces execute some logic from controller)

▪ Model – It is the Database, which stores Schema (Meta-Data(Data about Data) –> Apps, Tabs, sObjects, fields, Apex Classes, Visualforce pages, etc..) and Instance (Records)

▪ In Salesforce, whenever user create any component (Object, field, tab etc…) or record then salesforce will generate a unique id with which user can identify the record or component.

▪ After creating the record, in the URL user can see the id of the record which is of 15 digits length.

▪ Through user interface user always see 15-digit id which is Cases-Sensitive

▪ If the user query the existing records from the database through API (Either from Query Tool or from a program), it will always return 18 digit id which is Case-Insensitive.

▪ Last 3 digits of the 18 digit represents checksum of the capitalization of 15-digit id.

▪ Based on the first 3 digits user can identify the object of the record.

▪ All the records belongs to same object will contain same first 3 digits

▪ For an object based on the Record Type, we can show different fields and different picklist values by assigning different page layouts for the record types and profiles.

▪ After creating the record type, on the record type detail page user can see all the picklist data type fields, user can edit the picklist and decide which values should display for this particular record type.