↳

talk about the projects you worked and number of users you worked with and did you influence users to get them use the platform. Less

↳

I said I wanted to work for the company for 3-5 years as a business analyst.

↳

Sir, I am self motivated and hard working guy with positive attitude towards my life and my career. Less

↳

A permission set is a collection of settings and permissions that give users access to various tools and functions. Permission sets extend users' functional access without changing their profiles. Less

↳

Using order by desc and limit. Using indexing

↳

There are many reasons for it Altering data like Date-time Migrating the data types like currency Changing from multi-select picklist, checkbox, auto number to other types Altering to multi-select picklist from any type except picklist Changing to auto-number except from text Changing from text-area to e-mail, phone, URL, and text Less

↳

Each workflow rule applies to a single object, such as leads, accounts, or opportunities. For the maximum number of workflow rules allowed on an object, see Salesforce Editions and Limits. For standard objects, workflow rules can only perform field updates on the object related to the rule. The exceptions are that both Case Comments and Email Messages can perform cross-object field updates on Cases. For all custom objects, however, you can create workflow actions where a change to a detail record updates a field on the related master record. Cross-object field updates only work for custom-to-custom master-detail relationships. For example, in a custom recruiting application, create a workflow rule that sets the status of an application (the master object) to “Closed” when a candidate (the detail object) accepts the job. Or, for standard objects, create a rule to change the status of a case from “Awaiting Customer Response“ to “In Progress” when a customer adds a case comment. The cross-object field update function may depend on certain critical updates being active. Click Your Name | Setup | Critical Updates to see if your organization requires any updates. Workflow rules can't be triggered by campaign statistic fields, including individual campaign statistics and campaign hierarchy statistics. For a list of campaign fields that cannot trigger workflow rules, see Campaign Fields. Workflow rules can be triggered any time a record is saved or created, depending on your rule criteria. However, rules created after saving records aren't triggered by those records retroactively. Workflow rules are triggered when a standard object in a master-detail relationship is re-parented, even if the object's evaluation criteria is set to When a record is created, or when a record is edited and did not previously meet the rule criteria. Workflow rules only trigger on converted leads if validation and triggers for lead convert are enabled in your organization. Workflow rules on custom objects are automatically deleted if the custom object is deleted. You can't package workflow rules with time triggers. Workflow rules trigger automatically and are invisible to the user. Alternatively, approval processes allow users to submit records for approval. The order in which actions are executed is not guaranteed. Field update actions are executed first, followed by other actions. You can't create email alerts for workflow rules on activities. You can't create outbound messages for workflow rules on junction objects. To create workflow rules that update case fields based on new case comments or incoming email messages, choose Case Comment or Email Message from the Select Object drop-down list; Email Message is only available if Email-to-Case or On-Demand Email-to-Case is enabled. You can only create email message workflow rules for field updates, and case comment workflow rules for field updates, email alerts, and outbound messages. For example, you can create a workflow rule so that an email marked as Is Incoming changes its case's Status from Closed to New. Saving or creating records can trigger more than one rule. The following actions don't trigger workflow rules: Mass replacing picklist values Mass updating address fields Mass updating divisions Changing the territory assignments of accounts and opportunities Converting leads to person accounts Changes you make to records while using Connect Offline are evaluated by workflow rules when you synchronize. Salesforce processes any rules in the following order: Validation rules Assignment rules Auto-response rules Workflow rules (with immediate actions) Escalation rules Workflow rules and entry criteria for approval processes and steps respect the user's locale and aren't triggered when the user is in a different language than that of the organization. If a lookup field references a record that is deleted, Salesforce sets the lookup field to null, and does not run any Apex triggers, validation rules, workflow rules, or roll-up summary fields. Tip You can use the Developer Console to debug workflow rules. The Developer Console lets you view debug log details and information about workflow rules and actions, such as the name of the user who triggered the workflow rule and the name and ID of the record being evaluated. Less

↳

I answered the definition.

↳

Demonstrated the solution in a Dev-Ed sandbox