Shweta
IndividualForum Replies Created
-
Einstein Analytics comes with 3 layers i.e. Data Layer, Design Layer, and Intelligent Layer.
-
You can not assign a permission set to a public group directly.
-
We can use these deployment tools in Salesforce:
1. Change Sets
2. Eclipse IDE
3. Ant migration toolkit -
Permission Set Groups is a new feature that allows Admins to combine multiple permission sets into a single permission set group for user assignment. With the grouping mechanism, admins can truly apply role-based access control for managing user entitlements in Salesforce orgs.
-
Follow the below steps to add AccountTeamMembers using Data Loader:
1. Prepare a file with the following columns: AccountId, userId, TeamMemberRole, AccountAccessLevel, ContactAccessLevel, OpportunityAccessLevel, CaseAccessLevel.
2. Perform an Insert operation to the Account Team Member (AccountTeamMember) object, which should be available by selecting the "Show all Salesforce objects" option in the Data Loader, click Browse and select your file | Open | Next > | Ok
3. Click the Create or Edit a Map button and choose to Auto-Match Fields to Columns. Verify that the fields are properly mapped and click OK | Next>
4. Click Browse... to select the location on your local machine where you want to save the output files.
5. Click Finish and Yes at the prompt to proceed. -
Opportunities have a relationship with an Account record, and the Account has a relationship with Contacts – yet, no direct relationship. To get around this, Salesforce developed an object called 'Contact Roles', which creates a link between Contacts and the role they play in an Opportunity.
-
Lead is a person who is a sales prospect.
Opportunity is the specific sales deal being pursued including the estimated dollar amount. The Opportunity record will be related to the Lead or Contact record of the person with whom you are hoping to do business. -
You can associate actions to approval steps, initial submission, final approval, final rejection, or recall. Recall action will be executed if one of the approval process steps have been recalled.
-
Account Team is a predefined team that the Account Owner can set up, which can then be assigned to an Owner's accounts, when applicable. Notes: A User can only have one default account team.
-
Yes, You can do it with Dataloader.
-
Follow the below steps to create an Approval Process:
1. Go to SetUp → Enter Approval Process in Quick Find box → Select Approval Process.
2. For Manage Approval Process For, Select Opportunity.
3. Click Create New Approval Process → Select Use Jump Start Wizard.
4. Configure the approval process.
5. Save the approval process.
6. Click View Approval Process Detail Page.
7. Under Final Approval Actions, click Add New | Field Update, and configure it with your values.
8. Click Save
9. Under Final Rejection Actions, click Add New | Field Update, and configure it with your values.
10. Click Save -
Follow the below steps to enable the SOSL on custom settings:
Go to SetUp → Enter Schema Setting in Quick Find box → Select Schema Setting → Enable SOSL on Custom Setting. -
Follow the below steps to enable the list custom settings.
Go to SetUp → Enter Schema Setting in Quick Find box → Enable Manage List Custom Setting Type. -
When viewing a dashboard all steps are executed and any 'result' bindings will also automatically trigger to insert the desired values. In contrast 'selection' binding will need the user to click on the source step of the binding for the binding to execute and update the values.
-
Dashboard templates speed your Analytics development by automatically creating dashboards. Some provide blank layouts that you populate with data, while other “smart” templates create dashboards that require little to no additional configuration.
-
Yes, we have more than one Approver in the approval process.
-
You can query the fields in a big object's index using a subset of standard SOQL commands. Build an index query starting from the first field defined in the index, without gaps between the first and last field in the query. You can use = , < , > , <= , or >= , or IN on the last field in your query.
-
We need to implement the “force:appHostable” so that we can use the component as a Tab.
-
Tools included in Lightning:
Lightning Component Framework – Components and extensions that allow you to build reusable components, customize the Salesforce1 Mobile App, and build standalone apps.
Lightning App Builder – A new UI tool that lets you build apps lightning fast, using components provided by Salesforce and platform developers.
Lightning Connect – An integration tool that makes it easier for your Force.com app to consume data from any external source that conforms to the OData spec.
Lightning Process Builder – A UI tool for visualizing and creating automated business processes.
Lightning Schema Builder – A UI tool for viewing and creating objects, fields, and relationships. -
An invocable method will not accept more than one argument as a method parameter. Only static methods can be invocable methods and also More than one invocable method is not allowed per class.
-
Apex Flex Queue page lists all batch jobs that are in Holding status. You can view information about the job, such as the job ID, submission date, and Apex class. By default, jobs are numbered in the order submitted, starting with position 1, which corresponds to the job that was submitted first.
-
There are two main ways to use Async SOQL to get a manageable dataset out of a big object. The first is to use filtering. You can use filtering to extract a small subset of your big object data into a custom object. You can then use it in your reports, dashboards, or other nifty analytic tool.
-
You can create a wrapper with a list of objects like below and deserialize JSON to the wrapper.
Example:
Public class JSONtoApexClasses{
Public List<JSONtoApexClass> tickets {get; set;}
public class JSONtoApexClass{
public String SUMMARY;
public String CUSTOMERUSEREMAIL;
}
public static JSONtoApexClasses parse(String json) {
return (JSONtoApexClasses) System.JSON.deserialize(json, JSONtoApexClasses.class);
}
} -
System mode means running apex code by ignoring user's permissions. User mode means running apex code by respecting user's permissions and sharing of records.
-
With sharing Keyword enforces sharing rules that apply to the current user. If absent, code is run under the default system context. Use the with sharing keywords when declaring a class to enforce the sharing rules that apply to the current user.
Without sharing keyword ensures that the sharing rules of the current user are not enforced. Use the without sharing keywords when declaring a class to ensure that the sharing rules for the current user are not enforced. For example, you may want to explicitly turn off sharing rule enforcement when a class acquires sharing rules when it is called from another class that is declared using with sharing.