Salesforce Interview Questions

Terms in this set (283)

Before creating the Approval Process we should select the object after that we should follow below steps -
Give the Approval Process name
Give the criteria of the Approval Process
Select the email template (If we don't select any email template salesforce by default send an email notification to the target approver else with our selected email template target approver will be notified)
Select the users who can submit for the approval (If we do not select any user by default all the users who can access to that record can submit)
Select the user to whom record should be submitted
Initial submission actions ( after submitting the record for approval immediately whatever the actions included in the initial submission actions section will be triggered)
Approval Steps (we can add multiple steps)
For each and every step we can see 'Approval actions' and 'rejection actions' sections where we can add actions to be performed
If the Approver approves the record then actions which are under 'approval actions' section will be triggered
Final approval actions section (If all the steps approved then actions which are under 'final approval actions' section will be triggered)
Final rejection actions section (If any one of the step rejected then actions which are under 'final rejection actions' section will be triggered)
Recall approval actions ( After submitting record for approval if you want to revoke we click on recall approval action on the detail page, after clicking on that button actions which are under recall approval actions section will be triggered )
What is a Case?
- A logged issue or problem
• Similar Cases may be grouped using a Hierarchy
- Cases are:
• Manually entered from a phone call or an email
• Automatically create Case from an email (Emailto- Case)
• Automatically captured:
- Web site (Web-to-Case)
- Create a Case functionality in Outlook Edition
- May be assigned either manually or automatically via Assignment Rules
- Associated to Contacts and Accounts

What is a Case Queue?
- A virtual storage bin that can be used to group cases based on criteria such as skill requirements, product categories, customer
types, or service levels
- Users have visibility into the Case Queues to which they are members
- Cases remain in the Queue until they are assigned to or taken by individual users

What is a Case Assignment Rule?
- Determines how Cases are automatically routed to User or Queue
- Contains Rule Entries, pre-defined business rules, that determine Case routing

What is Web-to-Case?
- A web form that is published to a web site
- Customers use to submit inquiries online

What is Email-to-Case?
- Automatically create a case when an email is sent to one of your
company's email addresses, such as support@theblogreaders.com
What are Auto-Response Rules?
- Determines which Email Template to send to cases generated via Web-to-Case
- Contains Rule Entries that determine criteria for determining Email Template response content

What is an Escalation Rule?
- Automatically escalates an unresolved Case within a certain period of time (age over)
- Based on pre-defined business criteria

What are Business Hours?
- Set the organization's hours of operation
- Escalation Rule uses to determine when to escalate a Case
- Include business hours in multiple time zones.
- Associate cases with specific time zones
- Escalate cases according to specific time zones
The following is the order of salesforce execution when the you create or update a record,
1) Loads the original record from the database or initializes the record for an upsert statement.
2) Loads the new record field values from the request and overwrites the old values.
If the request came from a standard UI edit page, Salesforce runs system validation to check the record for:
Required values at the layout level and field-definition level
Valid field formats (ex: zip code, country code format)
Maximum field length (ex: mobile number must 10 digits)
Salesforce doesn't perform system validation in this step when the request comes from other sources, such as an Apex application or a SOAP API call.
3) Run all before triggers.
4) Runs most system validation steps again, such as verifying that all required fields have a non-null value, and runs any user-defined validation rules. The only system validation that Salesforce doesn't run a second time (when the request comes from a standard UI edit page) is the enforcement of layout-specific rules.
5) Saves the record to the database, but doesn't commit yet.
6) Run all after triggers.
7) Run assignment rules.
8) Run auto-response rules.
9) Run workflow rules.
10) If there are workflow field updates, updates the record again.
11) If the record was updated with workflow field updates, fires before and after triggers one more time (and only one more time), in addition to standard validations. Custom validation rules are not run again.
12) Run escalation rules.
13) If the record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the parent record. Parent record goes through save procedure.
14) If the parent record is updated, and a grand-parent record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the parent record. Grand-parent record goes through save procedure.
15) Run Criteria Based Sharing evaluation.
16) Commits all DML operations to the database.
17) Run post-commit logic, such as sending email.
1. Tabular: Tabular reports are the simplest and fastest way to look at data. Similar to a spreadsheet, they consist simply of an ordered set of fields in columns, with each matching record listed in a row. Tabular reports are best for creating lists of records or a list with a single grand total. They can't be used to create groups of data or charts, and can't be used in dashboards unless rows are limited. Examples include contact mailing lists and activity reports.

2. Summary: Summary reports are similar to tabular reports, but also allow users to group rows of data, view subtotals, and create charts. They can be used as the source report for dashboard components. Use this type for a report to show subtotals based on the value of a particular field or when you want to create a hierarchical list, such as all opportunities for your team, subtotaled by Stage and Owner. Summary reports with no groupings show as tabular reports on the report run page.

3. Matrix: Matrix reports are similar to summary reports but allow you to group and summarize data by both rows and columns. They can be used as the source report for dashboard components. Use this type for comparing related totals, especially if you have large amounts of data to summarize and you need to compare values in several different fields, or you want to look at data by date and by product, person, or geography. Matrix reports without at least one row and one column grouping show as summary reports on the report run page.

4. Joined: Joined reports let you create multiple report blocks that provide different views of your data. Each block acts like a "sub-report," with its own fields, columns, sorting, and filtering. A joined report can even contain data from different report types.
• Campaigns: A Campaign is any marketing project that you want to plan, manage, and track in Salesforce.
• Leads: A Lead is any person, organization or company that may be interested in your products. Sometimes Leads are referred to as Prospects or Suspects. Leads are not yet customers.
• Accounts: An Account is an organization, individual or company involved with your business such as customers, competitors and partners that you wish to track in Salesforce.
• Contacts: A Contact is any individual or influencer associated with an account that you want to track in Salesforce.
• Opportunities: An Opportunity is any potential revenue-generating event ("sales deal" ) that you want to track in Salesforce.
• Cases: A case is a detailed description of a customer's feedback, problem or question.
• Solutions: A solution is a detailed description of a customer issue and the resolution of that issue. The
collection of your organization's solutions is sometimes referred to as the solution knowledge base.
• Forecasts: A forecast is your best estimate of how much revenue you can generate in a quarter.
• Documents:
• Reports: Reports are summaries and analyses of your data, which you can display or print.
• Dashboards: Dashboards give you a real-time snapshot of corporate metrics and key performance
indicators. A dashboard is a group of different charts (or components) that graphically display your custom report data.
• Calendar and Task: Activities are both tasks and scheduled calendar events. You can define and track
activities for many different objects, including campaigns, accounts, contacts, and leads.
• Products: Products are the individual items that you sell on your opportunities. (Please note that Products are available in EE/UE and Developer and in PE for an additional fee.)
• Approval Request: An approval request is an email notifying the recipient that a record was submitted for approval and his or her approval is requested.

• Approval Steps: Approval steps assign approval requests to various users and define the chain of approval for a particular approval process.
- Each approval step specifies the attributes a record must have to advance to that approval step, the user who can approve requests for those records, and whether to allow the delegate of the approver to approve the requests.
- The first approval step in a process also specifies the action to take if a record does not advance to that step.
- Subsequent steps in the process also allow you to specify what happens if an approver rejects the request.

• Assigned Approver: The assigned approver is the user responsible for approving an approval request.

• Initial Submission Actions: are the actions that occur when a user first submits a record for approval.
- For example, an initial submission action can lock the record so that no users can edit it during the approval process.
- Initial submission actions can also include any approval actions such as assigning a task, sending an email, or updating a field.

• Final Approval Actions: are the actions that occur when all approval requests for a record are approved.
- Final approval actions can include any approval actions such as email alerts, field updates, tasks, or outbound messages.
- For example, a final approval action can change the status to "Approved" and send a notification email.

• Final Rejection Actions: are the actions that occur when all approval requests for a record are rejected.
- Final rejection actions can include any approval actions such as email alerts, field updates, tasks, or outbound messages.
- For example, a final rejection action can change the status to "Rejected", send a notification email, and unlock the record so that users can edit it before resubmitting.

• Record Locking: is the process of preventing users from editing a record regardless of field-level security or sharing settings.
- Records that are pending approval are automatically locked by Salesforce.
- Users must have the "Modify All Data" permission to edit locked records.
- The Initial Submission Actions, Final Approval Actions, and Final Rejection Actions related lists contain a record lock action that you can edit if necessary

• Outbound Messages: send the information you specify to an endpoint you designate.
- You can set up workflow rules and approval processes to send outbound messages to an endpoint as a means of getting information to an external service.


(Q). Approval Process Checklist

Use the following checklist to plan your approval process:
- Prepare an Approval Request Email
- Determine the Approval Request Sender
- Determine the Assigned Approver
- Determine the Delegated Approver
- Decide if your approval process needs a filter
- Decide initial submission actions
- Decide if users can approve requests from a wireless device
- Determine if users can edit records that are awaiting approval
- Decide if records should be auto-approved or rejected
- Determine how many levels your process has
- Determine the actions when an approval request is approved or rejected
An outbound change set contains customizations that you want to send from this organization to another organization. These customizations can include new components or modifications to existing components, such as apps, objects, reports, or Apex classes and triggers. An outbound change set can't be used to delete or rename components in another organization.

Example:
Deploy Apex classes and triggers developed in sandbox to production
Copy custom objects and other customizations to a sandbox without refreshing it
Migrate changes across environments, e.g. dev sandbox to QA sandbox to production

Advantage:
The change set remains active in organization for a period of time allowing for an audit of changes (beyond the setup audit trail). This functionality is in Sales force setup.
Change set can be include almost anything for example classes, pages, reports, objects, page layouts, record types, email templates etc.
Easy to deploy sandbox to production.
Authorize deployment connection.
Create outbound change set in sandbox environment.
Upload from Sandbox environment.
Review inbound change and deploy in production.
Faster as compare to all other tool like Eclipse IDE.

Disadvantage:
Lookup filter, labels, new picklist values, custom setting & labels are not available for deployments.
When creating new profiles first have to create a new profile (created in prod) and than add it to change set and avoid issues on profile based field dependency and page layout assignments.
Time based workflow trigger actions cannot be migrated.
When migrating workflows, you need to manually select the workflow rule and its actions separately.
No option of refreshing the change sets tool.
Not all metadata is supported in the metadata API which means some manual changes may need to be made in the production org.
To enable the distributed administrator to the upload a change set, you need to give them full rights in that sandbox, including the ability to manage users or modify all data