What is Salesforce?
Salesforce is the most popular customer relationship management (CRM) platform available today. It provides cloud-based CRM applications designed for use in sales, service, marketing, and much more. Businesses use Salesforce to manage business relationships and their associated data.
What is CRM?
CRM is an acronym for Customer Relationship Management, and it describes an application that helps businesses automate and digitize sales and marketing activity to manage (and increase) revenue. Sales and marketing professionals leverage CRM’s features to attract and retain customers and clients, thereby increasing sales.
Data Modeling Related Questions
What is an object in Salesforce?
An Objects is represented as a database table which stores organization data . Objects consists of set of fields and we store data against that field. To view data Salesforce provided TABS.
To create custom fields go to Setup=>Build=>Create=>Object.
Different types of object in Salesforce.com?
In Salesforce.com we have two types of objects. They are
- Standard Objects :- Standard objects are called so because they are created and provided by Salesforce.com.
- Custom Objects :- Custom objects are those which are created by an User in salesforce.com.
How many relationship types are in Salesforce?
- Master-detail
- Many-to-many
- Lookup
- External lookup
- Indirect lookup
- Hierarchical
What is Master-detail relationship?
Master-detail closely links objects together such that the master record controls certain behaviors of the detail and subdetail record. For example, you can define a two-object master-detail relationship, such as Account—Expense Report, that extends the relationship to subdetail records, such as Account—Expense Report—Expense Line Item. You can then perform operations across the master—detail—subdetail relationship.
What is Many-to-many relationship?
Many-to-many You can use master-detail relationships to model many-to-many relationships between any two objects. A many-to-many relationship allows each record of one object to be linked to multiple records from another object and vice versa. For example, you create a custom object called “Bug” that relates to the standard case object such that a bug could be related to multiple cases and a case could also be related to multiple bugs.
Lookup Links two objects together. Lookup relationships are similar to master-detail relationships, except they do not support sharing or roll-up summary fields. With a lookup relationship, you can:
- Link two different objects.
- Link an object with itself (with the exception of the user object; see Hierarchical). For example, you might want to link a custom object called “Bug” with itself to show how two different bugs are related to the same problem.
What is External lookup?
External lookup An external lookup relationship links a child standard, custom, or external object to a parent external object. When you create an external lookup relationship field, the standard External ID field on the parent external object is matched against the values of the child’s external lookup relationship field. External object field values come from an external data source.
What is Indirect lookup?
Indirect lookup An indirect lookup relationship links a child external object to a parent standard or custom object. When you create an indirect lookup relationship field on an external object, you specify the parent object field and the child object field to match and associate records in the relationship. Specifically, you select a custom unique, external ID field on the parent object to match against the child’s indirect lookup relationship field, whose values come from an external data source.
What is Hierarchical relationship?
Hierarchical A special lookup relationship available for only the user object. It lets users use a lookup field to associate one user with another that does not directly or indirectly refer to itself. For example, you can create a custom hierarchical relationship field to store each user’s direct manager.
For more details, please refer to this link Object Relationships Overview
What is a roll-up summary field?
A roll-up summary field calculates values from related records, such as those in a related list. You can create a roll-up summary field to display a value in a master record based on the values of fields in a detail record. The detail record must be related to the master through a master-detail relationship. For example, you want to display the sum of invoice amounts for all related invoice custom object records in an account’s Invoices related list. You can display this total in a custom account field called Total Invoice Amount.
Security related
What are different Levels of data access in Salesforce?
Organization level security
For your whole org, you can maintain a list of authorized users, set password policies, and limit logins to certain hours and locations.
Object level security
Access to object-level data is the simplest thing to control. By setting permissions on a particular type of object, you can prevent a group of users from creating, viewing, editing, or deleting any records of that object. For example, you can use object permissions to ensure that interviewers can view positions and job applications but not edit or delete them.
Field level security
You can restrict access to certain fields, even if a user has access to the object. For example, you can make the salary field in a position object invisible to interviewers but visible to hiring managers and recruiters.
Record level security
You can allow particular users to view an object, but then restrict the individual object records they’re allowed to see. For example, an interviewer can see and edit her own reviews, but not the reviews of other interviewers. You can manage record-level access in these four ways.
- Organization-wide defaults
- Role hierarchies
- Sharing rules
- Manual sharing
What is Organization-wide defaults?
Organization Wide Defaults(OWD) in salesforce is the baseline level of access that the most restricted user should have. Organizational Wide Defaults are used to restrict access. You grant access through other means like(sharing rules, Role Hierarchy, Sales Teams and Account teams, manual sharing, Apex Sharing ). In simple words Organization Wide Defaults(OWD)specify the default level of access users have to each other’s records.
For more details please level to below post Organization Wide Defaults(OWD) in salesforce
What is role hierarchy?
It give access for users higher in the hierarchy to all records owned by users below them in the hierarchy. Role hierarchies don’t have to match your organization chart exactly. Instead, each role in the hierarchy should represent a level of data access that a user or group of users needs.
What are the difference between a Role and Profile?
Roles are one of the ways you can control access to records. They also impact reports (e.g. “My Teams” filter). Roles come into play if your security model (OWDs) are set to private.
Profiles help determine record privileges. Assuming the User can see the record, Profiles determine what the User can do, view or edit on that record. Profiles control other system privileges as well (mass email, export data, etc)
In simple words, Roles are one of the ways you can control access to records and Profiles determine what the User can do, view or edit on that record.
What are Sharing Rules?
Sharing Rules are automatic exceptions to organization-wide defaults for particular groups of users, so they can get to records they don’t own or can’t normally see. Sharing rules, like role hierarchies, are only used to give additional users access to records. They can’t be stricter than your organization-wide default settings.
What is Manual sharing?
It allows owners of particular records to share them with other users. Although manual sharing isn’t automated like org-wide sharing settings, role hierarchies, or sharing rules, it can be useful in some situations, such as when a recruiter going on vacation needs to temporarily assign ownership of a job application to someone else.
What is Profile?
Each user has a single profile that controls which data and features that user has access to. A profile is a collection of settings and permissions. Profile settings determine which data the user can see, and permissions determine what the user can do with that data.
- The settings in a user’s profile determine whether she can see a particular app, tab, field, or record type.
- The permissions in a user’s profile determine whether she can create or edit records of a given type, run reports, and customize the app.
Profiles usually match up with a user’s job function (for example, system administrator, recruiter, or hiring manager), but you can have profiles for anything that makes sense for your Salesforce org. A profile can be assigned to many users, but a user can have only one profile at a time.
What are standard profiles?
- Read Only
- Standard User
- Marketing User
- Contract Manager
- System Administrator
What is Permission Set?
A permission set is a collection of settings and permissions that give users access to various tools and functions. The settings and permissions in permission sets are also found in profiles, but permission sets extend users’ functional access without changing their profiles.
Permission sets make it easy to grant access to the various apps and custom objects in your org, and to take away access when it’s no longer needed.
Users can have only one profile, but they can have multiple permission sets.
What is “View all” and “Modify all” permission?
View all and Modify all permissions are usually given to system administrator. When you grant “View All” or “Modify All” for an object on a profile or permission set, you grant any associated users access to all records of that object regardless of the sharing and security settings.
In essence, the “View All” and “Modify All” permissions ignore the sharing model, role hierarchy, and sharing rules that the “Create,” “Read,” “Edit,” and “Delete” permissions respect. Furthermore, “Modify All” also gives a user the ability to mass transfer, mass update, and mass delete records of that specific object, and approve such records even if the user is not a designated approver.
These tasks are typically reserved for administrators, but because “View All” and “Modify All” let us selectively override the system, responsibilities that are usually reserved for the administrator can be delegated to other users in a highly controlled fashion.
Is it possible to restrict permission for users using permission set?
No, Permission Set always extends the permission. It does not restrict permission to users.
If a user does not have access to a specific record type, will they be able to see the records that have that record type?
Yes, Record type controls only visibility of record on UI but not its access to users. If user does not have access to record type then user will not be able to create records for that record type using UI. But user will we able to see records if they have appropriate permission to do so.
Process Automation Related
What is workflow?
Workflow is a basic automation tool which allows Admins to trigger and action (such as updating fields or sending emails) when a certain data condition exists. They are the simplest type of automation to implement and also the most limited.
What is Process Builder?
Process Builder is a more advanced automation tool than Workflows. While still following the If This Happens, Then Do That concept, Process Builder allows Admin to control the order of actions as well as offering more actions such as creating records, posting to Chatter, and launching other automated tools.
What is a Flow?
Flow is the granddaddy of declarative automation tools. The logic required to perform actions is less rigid than the other tools, so you can do things like have branching decisions and looping through actions. You can also perform additional types of actions such as deleting records or creating/editing records unrelated to the original starting point. Beginning with Winter ’20 you can even schedule Flows to launch at a specific time rather than when something happens. The redesigned Flow Designer introduced in Spring ’19 really went a long way to make it feel like an Admin tool more than a Developer one. Finally, Flow is the only declarative automation tool that allows admins to build custom screens to interact with users and can greatly improve the user experience in Lightning (which is required for Screen Flows.)
What is an Approval Process?
An Approval Process is for very specific automation use cases. Naturally, it’s used when something needs to be approved and tracks when and who approved or rejected something. It covers notifying approvers, locking the record from edits, conditional logic for who should approve, and varied approval models (for example, all approvers or any approvers.)