Cloud computing means storing and accessing data and programs over the Internet instead of your computer's hard drive. What cloud computing is not about is your hard drive. When you store data on–or run programs from the hard drive, that's called local storage and computing.
• Copy configuration changes
• No real time data
• Sample data limit is 1GB
Refresh time interval one day
Production environments store the live data that is actively used to run your business.
We should not make coding changes in production since end-users are using the application from production environment.
To make any changes for the exiting application we should copy all contents of the production into sandbox and make all changes after that test thoroughly after that move those changes into production.
To create the sandbox, in production we can find one link called sandboxes. by clicking on that link we can create the sandbox by choosing type of the sandbox.
1. Developer Sandbox
2. Developer pro sandbox
3. Partial data sandbox
4. Full copy sandbox
• It copy only configuration changes from the production.
• It won’t copy real time data.
• We can test the configuration changes with sample data.
• Sample data limit is 200mb.
• Refresh time interval is one day.
• If we refresh all the sandbox contents will be replaced with production contents
• Copy configuration changes
• Copy certain amount of real time data
• Real time data limit is 5GB
• For each table it can copy maximum of 10k records
• Refresh interval 5 days
• It is exact replica of the production
• Copy both configuration and entire real time data from the production
• Refresh time interval 29 days
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 –
Task: Task is nothing but work assigned to a particular person, it doesn’t have certain time limit.
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 is 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.
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. It 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 field (Dependent field) from another field (Controlling field).
For 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, VF Pages, Fields and Record Types)
Controller – Business Logic (Save, Edit, New, Cancel and Delete – upon click on these button salesforce 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)