MOHIT
IndividualForum Replies Created
-
A report is a template which is used by users to display the information in well defined form. Report is displayed in tabular or graphical chart. It can be filtered, and grouped. Also you can organize the reports in a Folder. User can control the access on this folder by keeping public, hidden, shared or sometimes read only access. One can made the folder is accessible for entire organization or vice versa can be available for single person based on permissions.
Salesforce Dashboards
Dashboard is a page layout for visual display of your data. Each dashboard has 1:1 mapping for its component and report. One can clubbed multiple dashboard components to display a single report. The security settings is used to control the visibility of data. These dashboards are dynamic in nature. User can only view their own data as per their settings. -
Workflow:
Workflow enables you to set up workflow rules. A workflow rule identifies what kinds of record changes or additions trigger specified workflow actions, such as sending email alerts and updating record fields.
Workflow rules and actions are associated with a specific object (and can cross objects only to update fields on a related master record).
Visual Workflow:
Visual Workflow enables you to create flows, which are triggered by users rather than events. Unlike Workflow, which always executes rules and actions behind the scenes, Visual Workflow offers screens for displaying and collecting information from the user running the flow.
Flows aren’t tied to any one object. They can look up, create, update, and delete records for multiple objects.
Process Builder:
The Process Builder’s simple and powerful design allows you to:Create your processes using a convenient layout with point-and-click efficiency.
Create your whole process in one place rather than using multiple workflow rules.
Create processes by collaborating with different teams in your business.
Stop using Apex code to automate simple tasks. -
On the Leads home page, click the Import Leads link at the bottom of the page, below the Tools heading.
The Lead Import Wizard page appears, providing you with a four-step process to import your records, plus helpful hints.
In your existing lead file or system, compare your fields against the lead fields in Salesforce. Map all your fields between your current system and Salesforce.
If you can map all the necessary fields, move to the next step. If not, add fields to the lead record by customizing Salesforce.
While someone is mapping the fields from your current system to Salesforce, you should also be talking with your company about cleaning up that data. Now’s a good time to discuss which of your current system’s fields are still needed in the new world.
Some fields may have been used several years ago, but no one’s been filling them in since you can remember, and no one’s bothered to remove or hide them from the current system. Even worse, no one can recall what those fields were for, or maybe you have multiple fields with very similar names!
Also, you could have lots of duplicate or partial records. Discuss with your company and your Salesforce consultant about best approaches to cleaning up this information.
Mapping is a technical term for matching one field to another field, typically in different databases, to properly move data. For example, in Microsoft Outlook, you type a corporation’s name into the Company field.
In Salesforce, you typically use the Account Name field. These two different labels have the same meaning. Mapping is the process by which you decide that data from the Company field in Outlook should correspond to the Account Name field in Salesforce.
Export your file.
You might have leads in an existing database or spreadsheet, such as Microsoft Excel, Oracle CRM On Demand, or Microsoft Dynamics. Most systems like these have simple tools for exporting data into various formats. Select the records and the fields that you want. Then, export the file and save it in a format. If your leads are already in spreadsheet format (such as Excel), just resave the file in format.
Review your lead data.
You’ve probably heard the old adage “garbage in, garbage out.” Regardless of whether your company spent some time with initial housecleaning before this step, it’s important to review this data again at this point. Clean up your information before you bring it into Salesforce so that you can save yourself the effort later.
When you’re done with the preparation, click the Start the Import Wizard link on the Lead Import Wizard.
Complete the fields in Step 1 of the wizard.
Assuming that you already prepared your file, you probably just need to follow these steps:
Load the file by clicking the Choose File button and selecting the correct file on your computer.
Select a default lead source, if relevant.
Apply an assignment rule if you want leads to route directly to assigned reps.
If you don’t use an assignment rule, all the leads that you import are assigned to you unless you otherwise specify a lead owner in the file.
Select the check box if you want to use assignment rule settings to send e-mail notifications to the record owners.
Verify the character coding.
Salesforce prefills this picklist based on your company profile, and you rarely have to change it.
Select the matching type.
If you want Salesforce to avoid importing duplicate records, choose whether you want to identify a duplicate lead by matching Salesforce ID, name, or e-mail. If a lead record with the matching criteria already exists in Salesforce, that record is updated with the information in your file.
Select the check box if you want to trigger workflow rules to new and updated records.
When you’re done with Step 1 of the wizard, click Next.
The Field Mapping page appears.
Map the fields between your file and Salesforce and then click Next.
The Field Mapping page displays all the Salesforce lead fields as labels with drop-down lists that correspond to the fields in your file. Simply go through the list of fields and select the field from the corresponding file that you’re importing which maps to the Salesforce field, as shown in the figure.
After you click Next, the Review and Confirm page appears, displaying a list of warnings, if any, on your impending import.
Review the messages for possible errors.
This step basically warns you about problems with the data or lets you know about fields that you haven’t mapped. If you discover an error, you can click the Back button and refine your mapping, or even close the wizard so that you can improve your import file. You might have to start over, but at least you avoid importing bad or incomplete data.
When you’re satisfied with your mapping, click the Import Now button.
An Importing page appears to let you know that the import is in progress, including an estimate of how long it will take.
Click the Finish button.
The pop-up window closes.
Check the lead records that you imported.
Salesforce sends you an e-mail after your file has been successfully imported. To check your handiwork, click the Leads tab to go to your Leads home page. In the View drop-down list, select Today’s Leads to see a list of the leads that were created today. Click the link for a lead that you just imported and review the information for accuracy.
Importing leads is one of the fastest ways for you to set up your leads in Salesforce so that you can begin working them. -
Data Import Wizard feature of Salesforce helps you ease importing data in your Salesforce organization. The Data Import Wizard lets you import data not just in standard objects but in custom objects as well. It can import up to 50,000 records at a time.
Data Import Wizard can be used when
There are less than or equal to 50,000 records to be imported.
You do not want to schedule the import process. -
The Limits methods return the specific limit for the particular governor, such as the number of calls of a method or the amount of heap size remaining.
Each method has two versions. The first version returns the amount of the resource that has been used in the current context. The second version contains the word “limit” and returns the total amount of the resource that is available for that context. For example, getCallouts returns the number of callouts to an external service that have already been processed in the current context, while getLimitCallouts returns the total number of callouts available in the given context.
In addition to the Limits methods, use the startTest and stopTest methods to validate how close the code is to reaching governor limits.
The stopTest method marks the point in your test code when your test ends. Use this method in conjunction with the startTest method. Each test method is allowed to call this method only once. Any code that executes after the stopTest method is assigned the original limits that were in effect before startTest was called. All asynchronous calls made after the startTest method are collected by the system. When stopTest is executed, all asynchronous processes are run synchronously. -
definitions and page layouts, for your organization. This API is intended for managing customizations and for building tools that can manage the metadata model, not the data itself. To create, retrieve, update or delete records, such as accounts or leads, use data SOAP API or REST API.
The easiest way to access the functionality in Metadata API is to use the Salesforce Extensions for Visual Studio Code or the Ant Migration Tool. Both tools are built on top of Metadata API and use the standard tools to simplify working with Metadata API.
The Salesforce Extensions for Visual Studio Code includes tools for developing on the Salesforce platform in the lightweight, extensible VS Code editor. These tools provide features for working with development orgs (scratch orgs, sandboxes, and DE orgs), Apex, Aura components, and Visualforce.
The Ant Migration Tool is ideal if you use a script or the command line for moving metadata between a local directory and a Salesforce org.
For more information about the Salesforce Extensions for Visual Studio Code or the Ant Migration Tool, see Salesforce Tools and Toolkits.
The underlying calls of Metadata API have been exposed for you to use directly, if you prefer to build your own client applications. This guide gives you more information about working directly with Metadata API.
You can use the Metadata API to manage setup and customization information (metadata) for your organizations. For example:
Export the customizations in your organization as XML metadata files. See Working with the Zip File and retrieve().
Migrate configuration changes between organizations. See deploy() and retrieve().
Modify existing customizations in your organization using XML metadata files. See deploy() and retrieve().
Manage customizations in your organization programmatically. See CRUD-Based Metadata Development.
You can modify metadata in test organizations on Developer Edition or sandbox, and then deploy tested changes to production organizations on Enterprise, Unlimited, or Performance Editions. You can also create scripts to populate a new organization with your custom objects, custom fields, and other components. -
Workbench is a web-based tool which helps administrators and developers to interact with Salesforce for Data Insert, Update, Upsert, Delete and Export. It also supports the Undelete Program, Deploy, Retrieve, Rest Explorer and Apex Execute actions too. Workbench is an advanced tool that is built using JavaScript and PHP, where it supports more than 5 million records for Data manipulation!
For any Data Manipulations in Salesforce, we have Data Loader. To update one or two records using Data loader, we HAVE to export .CSV file, modify the excel file and then load it. But in case of Workbench, we can update a single record; we only require the 15 digit UniqueId of the record and update the fields as required. This is one of the best functionality of Workbench when compared to Data loader.
Uses:
In the browser, it is easy to read a table because of the simplified result information.
It is easy to build a SOQl query quickly.
It is easy to build SOSL function.
Using Workbench, the Purge option permanently deletes items from the recycle bin; Use 15 digit unique ID
It is User friendly, Simple to use which saves your settings through the session.
As Workbench is neither Supported, nor a Product of Salesforce, hence no support is provided by Salesforce. For any kind of support or issues we need to look for Open source communities. -
WhoID in Salesforce refers to people things. So that would be typically a Lead ID or a Contact ID. The WhoId represents a human such as a lead or a contact. WhoIds are polymorphic. Polymorphic means a WhoId is equivalent to a contact’s ID or a lead’s ID. The label is Name ID.
WhatID in Salesforce refers to object type things. That would typically be an Account ID or an Opportunity ID. The WhatId represents nonhuman objects such as accounts, opportunities, campaigns, cases, or custom objects. WhatIds are polymorphic. Polymorphic means a WhatId is equivalent to the ID of a related object. The label is Related To ID. -
Salesforce Lightning Migration from Salesforce Classic does not require to import the data, regenerate custom fields, or set up the security model. However, there are few aspects to the Lightning Experience that need a check during the migration of the data, such as:
Custom Code: The custom code created might not perform well in the Lightning version and might need to be addressed.
Business Processes: Going through the business processes again is advised to synchronize the requirements and experience how Lightning can overcome obstacles differently.
User Interface: The new Lightning Experience consists of 3-column layouts, up to 25 tabs, Paths, Components, etc.
3rd Party AppExchange Apps: With the Lightning-Ready 3rd party AppExchange apps, inventory management becomes much more feasible and attainable.
User Training: Current users need to be trained again to ensure that the adoption of new Lightning features is productive. -
A login flow directs users through a login process before they access your Salesforce org or community. You can use a login flow to control the business processes that your users follow when they log in to Salesforce. After Salesforce authenticates a user, the login flow directs the user through a process, such as enforcing strong authentication or collecting user information. When users complete the login flow successfully, they are redirected to their Salesforce org or community. If unsuccessful, the flow can log out users immediately.
-
Adobe Sign Merge Mappings give you the ability to merge field data from Salesforce into your documents fields before sending them out for signature.
For example, you can populate a Lead’s address and phone number from a Salesforce record automatically into the agreement before it is sent to the Lead for signature. You can also change the status of an Opportunity when the agreement is fully signed and executed. Merged data fields can optionally be updated by signers if you choose to map the signer updates back to Salesforce.
You can also use merge mappings to automatically add the product lists tied to an opportunity. You can set which product attributes (like quantity and price) are included in your agreements as well as specify how to sort and filter the associated products.
About Merge Mappings
A data source type for a merge mapping can be a specific constant value or a value from a Salesforce object field that can be referenced from the Adobe Sign Agreement. The target for each merge mapping item is a designated field on an Adobe Sign agreement.
For example, the mapping below updates the Adobe Sign document fields for “FirstName” and “LastName” with the Salesforce Recipient (Contact) field data. It also fills in the company field in the document with the name of the account. -
Adobe Sign form field data mappings let you define how Adobe Sign will update Salesforce.com objects with data it captures from signers. For example, you can update a signer’s contact record in Salesforce.com with the address and phone number they provided when completing and signing your document. Additionally, you can also push back the Adobe Sign signed agreement, audit trail, and any uploaded supporting documents from recipients into Salesforce objects by setting up file mappings.
About Form Field Data Mappings
Adobe Sign Data Mappings update Salesforce objects when an Adobe Sign agreement is signed or at a specified stage in the agreement workflow. Each Data Mapping is set up ahead of time and includes data mapping rules. Each data mapping rule defines the data source and the target Salesforce field it needs to update.
A data source for a mapping can be an Adobe Sign form field, a specific constant value or a value from an Adobe Sign Agreement Field. The target for each data mapping item may be any field in any Salesforce object that can be referenced from the Adobe Sign Agreement.
For example, the mapping below updates the signer’s first and last name (as entered by the signer) in the Contact object. It also updates the Opportunity Stage and adds the signed agreement and audit trail to the Opportunity when the agreement is signed. -
Adobe Sign gives you the ability to use interactive forms to collect data from your signers, position signature and initial fields in your documents, collect two-party information from both sender and signer and more.
You can create your own Adobe Sign template library by storing Adobe Sign forms and templates in your Salesforce Documents tab. -
apex:dataList
An ordered or unordered list of values that is defined by iterating over a set of data. The body of the <apex:dataList> component specifies how a single item should appear in the list. The data set can include up to 1,000 items. -
The Audit Trail helps you track the recent Setup changes that you and other administrators have made to your organization. This is especially useful in organizations with multiple administrators.
The setup Audit Trail history shows you the 20 most recent Setup changes made to your organization. It lists:
The date and time (with timezone) of the change.
Who made it (by username).
What the change was. -
apex:relatedList
A list of Salesforce records that are related to a parent record with a lookup or master-detail relationship. -
An app in Salesforce.com is nothing but a container which contains in it - a name, a logo, and an ordered set of tabs.
All the metadata such as Objects, Visualforce Pages, Classes, etc are independent of an app. An app just helps to group things together visually. But internally the metadata has nothing to do with an app i.e. you can have the same tab, VF Page in multiple apps. -
To expose a SOAP Web Service, do the following:
In the Logic tab, open the Integrations folder.
Right-click the SOAP element and select Expose SOAP Web Service.
Set the name of your SOAP Web Service and the remaining properties.
If you want to set a specific namespace for your SOAP Web Service, set it in the "Web Services Namespace" property of the module.
Right-click your new SOAP Web Service and select Add Web Service Method.
Set the name of your method.
Design the logic of your Web Service Method.
When you publish your module, the following happens:
The actions of exposed SOAP Web Services are translated into methods in the WSDL, with the same name and description.
The data types used by these actions are mapped into XML data types in the WSDL. -
@isTest(isParallel=true) annotation is used to indicate test classes that can run in parallel. Default limits on the number of concurrent tests do not apply to these test classes. This annotation makes the execution of test classes more efficient, because more tests can be run in parallel.
This annotation overrides settings that disable parallel testing. -
An inbound change set is a change set that has been sent from another Salesforce org to the org you are logged in to. A change set must be deployed for the changes to take effect. You can deploy the contents of an inbound change set as a whole but not on a component-by-component basis.
An outbound change set is a change set created in the Salesforce org in which you are logged in and that you want to send to another org. You typically use an outbound change set for customizations created and tested in a sandbox and that are then sent to a production org. -
WhoID in Salesforce refers to people things. So that would be typically a Lead ID or a Contact ID. The WhoId represents a human such as a lead or a contact. WhoIds are polymorphic. Polymorphic means a WhoId is equivalent to a contact’s ID or a lead’s ID. The label is Name ID.
WhatID in Salesforce refers to object type things. That would typically be an Account ID or an Opportunity ID. The WhatId represents nonhuman objects such as accounts, opportunities, campaigns, cases, or custom objects. WhatIds are polymorphic. Polymorphic means a WhatId is equivalent to the ID of a related object. The label is Related To ID. -
WhoID in Salesforce refers to people things. So that would be typically a Lead ID or a Contact ID. The WhoId represents a human such as a lead or a contact. WhoIds are polymorphic. Polymorphic means a WhoId is equivalent to a contact’s ID or a lead’s ID. The label is Name ID.
-
This reply was modified 4 years, 7 months ago by
Forcetalks.
-
This reply was modified 4 years, 7 months ago by
-
These are the Steps:
1) Sign in to Salesforce with a Salesforce administrator account.
2) Click Setup in the upper right of the page.
3) In the navigation pane, click Build > Develop > Visualforce Pages.
The right pane displays a list of the Visualforce pages.
4) In the middle of the page, click New.
The Page Edit page appears.
5) Enter the details for the Visualforce page.
a) In the Label box, type the Visualforce page label.
The name has the format COS CustomObjectName VF, for example COS Inventroy VF.
b) In the Name box, type the Visualforce page name.
The name has the format COS_CustomObjectName_VF, for example COS_Inventroy_VF.
c) In the Description box, type the Visualforce page description, for example "This page accesses the Commvault ObjectStore for the Inventory object".
The name has the format COS_CustomObjectName_VF, for example COS_Inventroy_VF.
6) On the Visualforce Markup tab, add the code snippet similar to the one below, substitute the CustomObjectAPI variable with the value that you noted from the Identifying the API Name for a Salesforce Custom Object procedure.
<apex:page standardController="CustomObjectAPI" showHeader="false" showChat="false" sidebar="false">
<c:COS_Component />
</apex:page>7) Click Save.
-
These are 5 types of sharing rules are there in Salesforce:
A. Case Sharing Rules
B. Lead Sharing Rules
C. Solution Sharing Rules
D. Campaign Sharing Rules
E. Custom Object Sharing Rules -
1. Go to Setup --> App Setup --> Create --> Tabs and click new button under visualforce tabs.
2. Select the visualforce page to which you want to create the tab and click "Next" button.
3. Click "Next" after the profile setting.
4. Select the application in which the Tab should be available and click "Save" button.
5. Click the tab to open the visualforce page.