[Parul]

lightning:tree component displays visualization of a structural hierarchy, such as a sitemap for a website or a role hierarchy in an organization. Items are displayed as hyperlinks and items in the hierarchy can be nested. Items with nested items are also known as branches.

[Parul]

Lightning was designed to follow an App-Centric model. This essentially means that it has been designed to create self-contained components that build on top of each other. To put this in perspective, with Visualforce you would send an interaction to the Salesforce server and then update the entire page. However, with Lightning, you can send an interaction to the Salesforce servers and then update a specific component. This has huge implications for performance and for the fluid motion of a UI. This allows us to design UIs that are inherently responsive to the user interactions, meaning we update the things the user is interacting with and everything else remains untouched.

[Parul]

To change styles dynamically, use $A.util.toggleClass() or $A.util.addClass(),$A.util.removeClass().
Use $A.util.toggleClass() for component instead of a DOM element.

//toggleCss.cmp
<aura:component>
   <div aura:id=”changeIt”>Change Me!</div><br />
   <ui:button press=”{!c.applyCSS}” label=”Add Style” />
   <ui:button press=”{!c.removeCSS}” label=”Remove Style” />
</aura:component>

//toggleCssController.js
({
   applyCSS: function(cmp, event) {
      var cmpTarget = cmp.find(‘changeIt’);
      $A.util.addClass(cmpTarget, ‘changeMe’);
   },
   removeCSS: function(cmp, event) {
      var cmpTarget = cmp.find(‘changeIt’);
      $A.util.removeClass(cmpTarget, ‘changeMe’);
   }
})

//toggleCss.css
.THIS.changeMe {
    background-color:yellow;
    width:200px;
}

[Parul]

Generally speaking, The Spring release is around February, the Summer release is around June, and the Winter release is around October.

[Parul]

Custom labels are custom text values that can be accessed from Apex classes, Visualforce pages, or Lightning components. The values can be translated into any language Salesforce supports. Custom labels enable developers to create multilingual applications by automatically presenting information (for example, help text or error messages) in a user's native language.

Create and Edit Custom Labels
1.From Setup, enter Custom Labels in the Quick Find box, then select Custom Labels.
2.To create a label, click New Custom Label. To edit a label, click Edit next to the custom label.
3.In the Short Description text box, enter an easily recognizable term to identify this custom label. This description is used in merge fields.
4.If you’re creating a custom label: In the Name text box, enter the name the label uses. This value is used in Apex and Visualforce pages to reference the custom label. Names must contain only alphanumeric characters, start with a letter, contain no spaces or double underscores, and be unique from all other labels in your org.
5.To mark the custom label as protected, check Protected Component..
6.For Categories, enter text to categorize the label. This field can be used in filter criteria when creating custom label list views. Separate each category with a comma. The total number of characters allowed in the Categories text box is 255.
7.In the Value text box, enter text up to 1,000 characters. This value can be translated into any language that Salesforce supports.
8.Click Save.

[Parul]

Database.com is a database. It will allow customers to develop applications for social, cloud, and mobile on the same platform on which Salesforce.com is built. The big advantage being cited is flexibility-applications can be written in any language and run on many different platforms including Force.com, VMforce, Amazon EC2, Google AppEngine, Heroku, and Microsoft Azure. Customers can also port existing databases to Database.com.

[Parul]

Developer Sandbox
A Developer sandbox is intended for development and testing in an isolated environment. A Developer Sandbox includes a copy of your production org’s configuration (metadata).

Developer Pro Sandbox
Use a Developer Pro sandbox to handle more development and quality assurance tasks and for integration testing or user training.

Partial Copy Sandbox
A Partial Copy sandbox is intended to be used as a testing environment.

Full Sandbox
A Full sandbox is intended to be used as a testing environment.

Thanks.

[Parul]

Filtering options for tables or ranges. You can either apply a general Filter option or a custom filter specific to the data type. For example, when filtering numbers, you'll see Number Filters, for dates you'll see Date Filters, and for text you'll see Text Filters.

I have to display the ouputPanel for each and every user in the org whose role is manager.
I can't assign name of the user directly using text in rendered attribute, since I dont know the names of users in the org where this page will be used.

I want dynamic way where I can render the outputPanel for each and every user in the above mentioned count.
The purpose behind the decrement is, it should cover all the users in the count.

[Parul]

Integer Count = [Select Count() from User where UserRole.Name =: 'Manager'];
Count holds the integer count of no of users in the organisation.

[Parul]

Integrate Salesforce with Outlook
There are two options to get connected with Outlook from Salesforce, one is by using “Salesforce for Outlook” option and another is by using “Connect for Microsoft Outlook”. Well, mostly the option “Connect for Microsoft Outlook” is being selected by the users. Let’s discuss both the ways in the following sections.
Salesforce for Outlook
The integration of Salesforce and Outlook is not only about emails, even Salesforce CRM can be easily synchronized with Microsoft Outlook and below-listed operations are performed automatically in this synchronization:

All contacts, tasks, and events are automatically synchronized between Outlook and Salesforce
Outlook emails are manually added to Accounts, Contacts, Lead Objects and Opportunities
Email attachments are uploaded to Salesforce.com
A new case has to be created in Salesforce for Outlook email
Contacts, calendar events, and tasks are associated in Outlook with the records

[Parul]

Caching is the ability to store copies of frequently accessed data in several places along the request-response path. When a consumer requests a resource representation, the request goes through a cache or a series of caches (local cache, proxy cache or reverse proxy) toward the service hosting the resource. If any of the caches along the request path has a fresh copy of the requested representation, it uses that copy to satisfy the request. If none of the caches can satisfy the request, the request travels all the way to the service (or origin server as it is formally known).

Using HTTP headers, an origin server indicates whether a response can be cached and if so, by whom, and for how long. Caches along the response path can take a copy of a response, but only if the caching metadata allows them to do so.

Optimizing the network using caching improves the overall quality-of-service in following ways:

Reduce bandwidth
Reduce latency
Reduce load on servers
Hide network failures

[Parul]

In the context of REST APIs, when making multiple identical requests has the same effect as making a single request – then that REST API is called idempotent.

When you design REST APIs, you must realize that API consumers can make mistakes. They can write client code in such a way that there can be duplicate requests as well. These duplicate requests may be unintentional as well as intentional some time (e.g. due to timeout or network issues). You have to design fault-tolerant APIs in such a way that duplicate requests do not leave the system unstable.

[Parul]

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.

[Parul]

First, you need to upload the image file to Documents, make it available for external use, and then capture it's ID from the address bar. Reference it in the formula below DocumentID. Replace Image Name with the word(s) you want to appear if the Image cannot be displayed. Replace Custom_URL_Field__c with the field name of your URL field.

HYPERLINK(Custom_URL_Field__c, IMAGE("servlet/servlet.FileDownload?file=DocumentID", "Image Name"))

[Parul]

Fields you create on standard or custom objects are called custom fields.

A data type indicates what kind of information the field stores. Salesforce supports a bunch of different data types, but here are a few you'll run into. Checkbox—for fields that are a simple “yes” or “no,” a checkbox field is what you want.

[Parul]

Salesforce supports many different field types. Pick the right type, or convert an existing one.

When you have data that doesn’t match any of the standard fields, your administrator can create a custom field for that data. For example, you might want a Middle Name field for contacts.

The first step in creating a custom field is choosing the type of the field. Below is a description of each custom field type. Additional field types may appear if an AppExchange package using those field types is installed.

[Parul]

1. The original record is loaded from the database (or initialized for an insert statement)
2. The new record field values are loaded from the request and overwrite the old values
3. All before triggers execute (TRIGGERS)
4. System validation occurs, such as verifying that all required fields have a non-null value, and running any user-defined validation rules (VALIDATIONS)
5. The record is saved to the database, but not yet committed
6. All after triggers execute
7. Assignment rules execute
8. Auto-response rules execute
9. Workflow rules execute (WORKFLOW)
10. If there are workflow field updates, the record is updated again
11. If the record was updated with workflow field updates, before and after triggers fire one more time (and only one more time)
12. Escalation rules execute
13. All DML operations are committed to the database
14. Post-commit logic executes, such as sending email

[Parul]

Custom Object Tabs — For your custom object data. Custom Object Tabs display the data of your custom object in a user interface tab. Custom object tabs look and function just like standard tabs.

Web Tabs — For other web content Custom Web Tabs display any external Web-based application or Web page in a Salesforce tab.

[Parul]

Please follow below salesforce Best Practice for Test Classes :-

1. Test class must start with @isTest annotation if class class version is more than 25
2. Test environment support @testVisible , @testSetUp as well
3. Unit test is to test particular piece of code working properly or not .
4. Unit test method takes no argument ,commit no data to database ,send no email ,flagged with testMethod keyword .
5. To deploy to production at-least 75% code coverage is required
6. System.debug statement are not counted as a part of apex code limit.
7. Test method and test classes are not counted as a part of code limit
9. We should not focus on the percentage of code coverage ,we should make sure that every use case should covered including positive, negative,bulk and single record .
Single Action -To verify that the the single record produces the correct an expected result .
Bulk action -Any apex record trigger ,class or extension must be invoked for 1-200 records .
Positive behavior : Test every expected behavior occurs through every expected permutation , i,e user filled out every correctly data and not go past the limit .
Negative Testcase :-Not to add future date , Not to specify negative amount.
Restricted User :-Test whether a user with restricted access used in your code .
10. Test class should be annotated with @isTest .
11 . @isTest annotation with test method is equivalent to testMethod keyword .
12. Test method should static and no void return type .
13. Test class and method default access is private ,no matter to add access specifier .
14. classes with @isTest annotation can't be a interface or enum .
15. Test method code can't be invoked by non test request .
16. Stating with salesforce API 28.0 test method can not reside inside non test classes .
17. @Testvisible annotation to make visible private methods inside test classes.
18. Test method can not be used to test web-service call out . Please use call out mock .
19. You can't send email from test method.
20.User, profile, organization, AsyncApexjob, Corntrigger, RecordType, ApexClass, ApexComponent ,ApexPage we can access without (seeAllData=true) .
21. SeeAllData=true will not work for API 23 version eailer .
22. Accessing static resource test records in test class e,g List<Account> accList=Test.loadData(Account,SobjectType,'ResourceName').
23. Create TestFactory class with @isTest annotation to exclude from organization code size limit .
24. @testSetup to create test records once in a method and use in every test method in the test class .
25. We can run unit test by using Salesforce Standard UI,Force.com IDE ,Console ,API.
26. Maximum number of test classes run per 24 hour of period is not grater of 500 or 10 multiplication of test classes of your organization.
27. As apex runs in system mode so the permission and record sharing are not taken into account . So we need to use system.runAs to enforce record sharing .
28. System.runAs will not enforce user permission or field level permission .
29. Every test to runAs count against the total number of DML issued in the process .

[Parul]

While creating a record, job must be scheduled but, If i schedule more than 100 jobs (i.e., create more than 100 records manually) of type schedule apex i am getting You have exceeded the maximum number (100) of Apex scheduled jobs. In this case scheduling itself is a problem . And i've gone through the concept flexiqueue but it is not available in current version.

[Parul]

A profile is a group/collection of settings and permissions that define what a user can do in Salesforce. A profile controls “Object permissions, Field permissions, User permissions, Tab settings, App settings, Apex class access, Visualforce page access, Page layouts, Record Types, Login hours & Login IP ranges.

[Parul]

Developer Sandbox
Developer sandboxes are special configuration sandboxes intended for coding and testing by a single developer. Multiple users can log into a single Developer sandbox, but their primary purpose is to provide an environment in which changes under active development can be isolated until they’re ready to be shared. Just like Developer Pro sandboxes, Developer sandboxes copy all application and configuration information to the sandbox. Developer sandboxes are limited to 200 MB of test or sample data, which is enough for many developments and testing tasks. You can refresh a Developer sandbox once per day.

REFRESH LIMIT:- Daily
DATA LIMIT:- 200MB

Developer Pro Sandbox
The main difference between this and Developer is the amount of data that can be stored. It also grabs some product data from production. If those two things are important, use this one. Otherwise, it's interchangeable with Developer
Developer Pro sandboxes copy all of your production organization's reports, dashboards, price books, products, apps, and customizations under Setup, but exclude all of your organization's standard and custom object records, documents, and attachments. Creating a Developer Pro sandbox can decrease the time it takes to create or refresh a sandbox from several hours to just a few minutes, but it can only include up to 1 GB of data. You can refresh a Developer Pro sandbox once per day

REFRESH LIMIT:- Daily
DATA LIMIT:- 1GB

Partial Copy
Partial Data sandboxes include all of your organization’s metadata and add a selected amount of your production organization's data that you define using a sandbox template. A Partial Data sandbox is a Developer sandbox plus the data you define in a sandbox template. It includes the reports, dashboards, price books, products, apps, and customizations under Setup (including all of your metadata). Additionally, as defined by your sandbox template, Partial Data sandboxes can include your organization's standard and custom object records, documents, and attachments up to 5 GB of data and a maximum of 10,000 records per selected object. A Partial Data sandbox is smaller than a Full sandbox and has a shorter refresh interval. You can refresh a Partial Data sandbox every 5 days.

REFRESH LIMIT:- 5 Days
DATA LIMIT:- 5GB

Full Sandbox
Full sandboxes copy your entire production organization and all its data, including standard and custom object records, documents, and attachments. You can refresh a Full sandbox every 29 days.
Sandbox templates allow you to pick specific objects and data to copy to your sandbox, so you can control the size and content of each sandbox. Sandbox templates are only available for Partial Data or Full sandboxes.

REFRESH LIMIT:- 29 Days
DATA LIMIT:- Same as Production

[Parul]

future method call that performs more processing on the same record(s). The issue is that this entire process becomes recursive in nature and you receive the error "System.AsyncException: Future method cannot be called from a future method.

[Parul]

Create a Data Extension
Follow these steps to create a data extension in Marketing Cloud Contact Builder.

Click Data Extensions.
Click Create.
Select the data extension method in the Creation Method dropdown menu:
Create from New - create a data extension and manually insert all attributes
Create from Existing - create a data extension and include all attributes assigned via the existing data extension, or add attributes later in the creation process
Create from Template - create a data extension and include all attributes assigned in the template, or you can add attributes later in the creation process
Enter a name for the data extension in the Name field.
Note the external key provided in the External Key field. Use the provided external key or enter a unique key of your own in this field. Each data extension must use a unique external key.
Enter a brief description of the data extension in the Description field.
Click Change Location and choose the location for storing the data extension:
To use an existing folder, click the folder and click OK.
To create a folder, click Create New Folder and name your folder. Select that folder when you complete the creation process.
Select the Is Sendable? checkbox to make this data extension available as the source of a send.
Select the Is Testable? checkbox to make this data extension available for testing.
Click Next.
To set a data retention policy for your data extension, click On under Data Retention.
To apply the data retention policy, click the button under the Apply To heading for the entity or entities.
Click the appropriate button under the Retention Period heading:
For a revolving time period, enter the number in the text field. Select the unit of measure in the dropdown menu next to the first button. For example, you could enter the number 6 and select Months in the dropdown menu to enforce a 6-month data retention policy.
For a set date, select the date next to the second button.
Click Next.
To make the attribute include the unique identifier for all records within the data extension, choose the Primary Key checkbox.
Enter a name for the attribute in the Name field.
Choose a data type from the Data Type dropdown menu.
For decimal data types, enter the maximum amount of numbers in the first text field. Enter the amount of numbers to appear to the right of the decimal point in the second text field.
Base16Encrypted
Base16EncryptedEmail
Boolean
Byte
Date
Decimal
EmailAddress
Locale
LongNumber
Number
Phone
ShortNumber
Text
If the attribute must contain a value for every contact, choose Required.
To allow in this attribute in the Length field, enter the number of characters.
To force the attribute to contain a value by default, enter that value in the Default Value text field.
Note
Repeat steps 12 through 17 for more attributes within the data extension.
Click Create.
Click OK.

[Parul]

Soft Bounce
A soft bounce occurs when the email server rejects the email message due to a seemingly temporary condition, such as:

Address is temporarily unavailable due to an inactive or temporarily disabled mailbox
Recipient's mailbox is full
Temporary domain failure
The Marketing Cloud will make 288 attempts to deliver the email message. If all attempts are unsuccessful, it is considered a soft bounce.

Types of soft bounces include:

• Block Bounce: Occurs when the email server rejects the email message due to filter issues, such as:
  Complaints
  Blacklisted IP address
  Content-related issues
  URLs within the email message are blocked
  Improper authentication
• Technical Bounce: Occurs when the email server rejects the email message due to technical errors, such as:
  The server is too busy/temporarily overwhelmed
  Formatting or line length errors
  Network connection lost or timed out

Hard Bounce
A hard bounce is an email message that is undeliverable for permanent reasons, such as:

Bad/nonexistent domain
Invalid or fake email address
High number of unknown/inactive addresses on a list