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
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 >
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.
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)
Normally, when a Salesforce user pulls the id from a record through the interface on any object they get the 15 digit id by design. So, if you created a report on Leads / Account / Contacts or any custom object and add the id field through the interface it will look something like 0015000001Fn4VL.
However, if you were to access that same Salesforce account id via an API or a tool like this from the Apex Data-loader & workbench 0015000001Fn4VLAAZ.
If you would like to convert the current user interface id to 18 digits this can be done by using a formula very simple formula. I have seen a couple of versions of the formula but this is the one that worked best for me in my career.
All you need to do is add a new formula field, text 18 characters with “CASESAFEID(ID)”
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.
Whenever user try to create a new record or edit an existing record user can input the values for the fields, this page is nothing but edit page.
After creating a new record or editing an existing record, user can see the information of the record, this page is nothing but detail page.
Functionalities are available within the Salesforce platform (i.e. no need to code).
While creating or modifying the record based on the certain conditions we can display error messages on top of the page or below to the filed.
Using vlookup function in the validation rule we can achieve this.
Since we are working in multitenant environment Salesforce is enforcing the limits for all the functionalities.
Text, number, auto number, email.
List View allows you to see a filtered list of records, such as contacts, accounts, or custom objects. List views are stored within a Custom Object component. The component can represent a custom object or a standard object, such as an account.
After clicking on the tab on the top of the page we can see views, by default we can see the value called ‘all’. If we click on ‘Go’ beside that all we can see all the records of that object.
We can create new views and while creating the view we can give the filter conditions so that based on the filter condition we will be able to see records in tab.
On the detail page without clicking on edit button we can edit particular field if it is not read-only.
To enable or disable Inline editing follow the below navigation – Setup–> Customise–> User Interface–> Enable Inline Editing
In list views we can modify multiple records at a time using Enhanced list views Note: To modify multiple records, all the records should belong to same record type in the list view otherwise we cannot modify.
Whenever we click on a tab or we click on a lookup icon or search for a record we see only one standard field by default, to enable remaining fields –
For lookup fields on record detail page we see a link, whenever we put cursor on that link we see a popup window which displays few fields. To control the fields visibility, on that look up field parent object page layout we see a mini page layout in that we can control.
To control the picklist values of the status field on the lead object we should create lead process. Without selecting the lead process we can’t create the record type for lead object
To control the picklist values of the stage field on the opportunity object we should create sales process. Without selecting the sales process we can’t create the record type for opportunity object
To control the picklist values of the status field on the case object we should create support process. Without selecting the support process we can’t create the record type for case object
On lead object we can generate the HTML code by selecting lead fields and by mentioning return URL from web-to-lead option. The generated HTML code can be hosted in any of the website. Upon entering the information in those fields and clicking on submit button that information will be saved into lead object of the Salesforce.
In queue we can add group of users and we can assign the objects to the Queue. After creating the queue one of the list view automatically created on the objects which are selected for the queue. We can assign this queue as the owner of the records (objects which are selected for this queue). Later users who are part of that queue can claim the ownership by navigating to list view corresponding to the queue. In that list view users who are part of the queue can select the record and click on accept button so that record ownership will be transferred from queue to accepted person.
We can add set of random users in the public group. We can’t assign public group as an owner of the record. In manual sharing, sharing rules and in list views we can use public group.
Assignment rules are used to automate your organization’s lead generation and support processes.
Lead Assignment Rules – Specify how leads are assigned to users or queues as they are created manually, captured from the web, or imported via the lead import wizards.
Case Assignment Rules – Determine how cases are assigned to users or put into queues as they are created manually, using Web-to-Case, Email-to-Case, On-Demand Email-to-Case, the Self-Service portal, the Customer Portal, Outlook, or Lotus Notes.
Aim: All the cases created by user ‘ABCUser’ should be assigned to ‘XYZUser’.
An auto-response rule is a set of conditions for sending automatic email responses to lead or case submissions based on the attributes of the submitted record. Applicable leads include those captured through a Web-to-Lead form. Applicable cases include those submitted through a:
Create case escalation rules to escalate cases automatically if they are not resolved within a certain period of time.
Typically, your organization will have one escalation rule that consists of multiple entries which specify exactly how the cases are escalated. For example, your standard case escalation rule could have two entries: Cases with Type set to Gold are escalated within two hours, and cases with Type set to Silver are escalated within eight hours. Goto Setup | Customize | Cases | Escalation Rules.