[Parul]

What is a hybrid cloud?
Often called “the best of both worlds,” hybrid clouds combine on-premises infrastructure, or private clouds, with public clouds so organisations can reap the advantages of both. In a hybrid cloud, data and applications can move between private and public clouds for greater flexibility and more deployment options. For instance, you can use the public cloud for high-volume, lower-security needs such as web-based email and the private cloud (or other on-premises infrastructure) for sensitive, business-critical operations like financial reporting. In a hybrid cloud, “cloud bursting” is also an option. This is when an application or resource runs in the private cloud until there is a spike in demand (such as seasonal event like online shopping or tax filing), at which point the organisation can “burst through” to the public cloud to tap into additional computing resources.

Advantages of hybrid clouds:
Control—your organisation can maintain a private infrastructure for sensitive assets.
Flexibility—you can take advantage of additional resources in the public cloud when you need them.
Cost-effectiveness—with the ability to scale to the public cloud, you pay for extra computing power only when needed.
Ease—transitioning to the cloud does not have to be overwhelming because you can migrate gradually—phasing in workloads over time.

Hybrid cloud is a cloud computing environment that uses a mix of on-premises, private cloud and third-party, public cloud services with orchestration between the two platforms.

Public clouds such as Amazon EC2 and Microsoft Azure have a number of benefits:

Utility Model – Public clouds typically deliver a pay-as-you-go model, where you pay by the hour for the compute resources you use. This is an economical way to go if you’re spinning up and tearing down development servers on a regular basis.
No Contracts – Along with the utility model, you’re only paying by the hour – if you want to shut down your server after only 2 hours of use, there is no contract requiring your ongoing use of the server.
Shared Hardware – Because the public cloud is by definition a multi-tenant environment, your server shares the same hardware, storage and network devices as the other tenants in the cloud.
Self Managed – With the pay-as-you-go utility model, self managed systems are required for this business model to make sense. There is an advantage here for the technical buyers that like to setup and manage the details of their servers, but a disadvantage for those that want a fully managed solution.
Most public cloud deployments are generally used for web servers or development systems where security and compliance requirements of larger organizations and their customers is less of an issue.

[Parul]

“created and every time it is edited”: 

Evaluate the rule criteria each time a record is created or updated. If the rule criteria is met, run the rule. With this option, the rule repeatedly runs every time a record is edited as long as the record meets the rule criteria.

“created and any time it is edited to subsequently meet criteria”:

(Default) Evaluate the rule criteria each time a record is created or updated.

For a new record, run the rule if the rule criteria is met.
For an updated record, run the rule only if the record is changed from not meeting the rule criteria to meeting the rule criteria.
With this option, the rule can run multiple times per record, but it won’t run when the record edits are unrelated to the rule criteria.

For example, suppose that for an opportunity record to meet the rule criteria, the opportunity probability must be greater than 50%. If you create an opportunity with a probability of 75%, the workflow rule runs. If you edit that opportunity by changing the probability to 25%, the edit doesn't cause the rule to run. If you then edit that opportunity by changing the probability from 25% to 75%, the edit causes the rule to run. With this last edit, the rule runs, because the record is changed from not meeting the rule criteria to meeting the rule criteria.

“When a record is created, or when a record is edited and did not previously meet the rule criteria” means that once it meets the criteria, it won’t fire again the next time the record is edited and saved.

“Every time a record is created or edited” means that even if it already fired once the last time the record was edited, it will fire again if it still meets the criteria.

Thanks

[Parul]

Leads Process

Every contact you get from these campaigns is added to the system as a lead. A lead is basically a business card with a name, address and phone number that could potentially be interested in your product. You either acquire this card in person, mail or lists. You have activities related to the lead development which will include calls, sending materials and possible meetings. A lead has a life cycle with lead stages and status. As a lead moves through the life cycle you can capture the time it took to move from one stage to another. Lead scoring also plays a huge part in prioritizing lead management.
There is a lot of debate on when is it right to convert a lead to an Account, Contact and Opportunity. I always advise on converting a lead when there is even a 10% chance of getting business from that lead.

[Parul]

Support Process is only for the "Status" picklist, as you might know. The picklist values available in the status of a case record type determine a support process. It is only a business relevant feature as the status field is the most process-specific field on a case. The status field cannot be customized on a record type, it can only be customized in a support process.

Leads Process - Every contact you get from these campaigns is added to the system as a lead. A lead is basically a business card with a name, address and phone number that could potentially be interested in your product. You either acquire this card in person, mail or lists. You have activities related to the lead development which will include calls, sending materials and possible meetings. A lead has a life cycle with lead stages and status. As a lead moves through the life cycle you can capture the time it took to move from one stage to another. Lead scoring also plays a huge part in prioritizing lead management.
There is a lot of debate on when is it right to convert a lead to an Account, Contact and Opportunity. I always advise on converting a lead when there is even a 10% chance of getting business from that lead.

Thanks,

[Parul]

A sales process is used to determine which opportunity stages are selectable when record types are enabled.  A sales process is not required if record types are not enabled.

Every company is unique, but all companies want to find, sell to, and keep customers. Salesforce has the tools you need to grow your pipeline and make more sales.

Salesforce features designed to support your sales process include leads, campaigns, products, pricebooks, opportunities, and quotes. In this section, we’ll learn about leads and opportunities. You can use opportunities alone, or you can enhance your opportunities by using them along with leads.

Setting up a sales process:

You might sell different items using different processes. You must set up at least one sales process in Salesforce, but you can set up additional processes to match how your business actually works.From Setup, click Customize | Opportunities | Sales Processes.
Click New.
To create the first new process for your organization, create a Master process.
Give your sales process a unique but descriptive name. For example, Retail Sales.
Optionally, add a description.
By default, all stages are included in a new process. Remove stages you don’t want to include by clicking the stage name in the Selected Values area, and then clicking the Remove arrow to move the unwanted stage to the Available Values area. For example, if you qualify all leads before converting leads to opportunities, remove Qualification from the selected values.
Click Save.

[Parul]

Customization in service cloud

•any feature or functions which are not available as a part of application and the application needs to extend refers to customization.

•despite you configured the things there are few actions which are not achievable and it results into adding some custom code, which results in Customization.

• Adding triggers on the object to perform some action is called customization

• Adding Apex Code which will generate a vCard from a given Contact is called Customization.

[Parul]

Software as a service (or SaaS) is a way of delivering applications over the Internet—as a service. Instead of installing and maintaining software, you simply access it via the Internet, freeing yourself from complex software and hardware management.

SaaS applications are sometimes called Web-based software, on-demand software, or hosted software. Whatever the name, SaaS applications run on a SaaS provider’s servers. The provider manages access to the application, including security, availability, and performance.

SaaS Characteristics:

Multitenant Architecture, Easy Customisation, Better Access, SaaS Harnesses the Consumer Web, SaaS Trends

The major benefit of SaaS is that you have no hardware or software to buy, install, maintain or update – so as a customer there’s little to see until you actually start using the software. Here are some common features of SaaS services.

Multi-tenancy cloud architecture
All users and applications share a common infrastructure that is centrally maintained. In terms of security, for example, this means that every user gets the highest level of security specified in your package.

Simple access
Via any networked device, making it easier to manage to access data and information and keep data in sync.

Familiar web-based interfaces
Building on the consumer web that users already know. This can help you boost adoption and take-up rates.

Accelerated feature delivery
With updates often rolled out weekly or monthly and no need to maintain or support legacy versions of the software.

Open integration protocols and APIs
Enabling the development of ‘mash-ups’ which combine data, presentation and functionality from multiple services.

Collaborative and social functions
Which allow people in different teams and or locations work co-operatively with one another.

[Parul]

There are 2 types of SOQL Statements.

Static SOQL:

Static SOQL means you are using some SOQL with any user input or hard code values like below query view source
List<Account> lstAccount = [select id,name form account where name ='Amit'];

Dynamic SOQL:

Dynamic SOQL refers to the creation of a SOQL string at runtime with Apex code. Dynamic SOQL enables you to create more flexible applications. For example, you can create a search based on input from an end user, or update records with varying field names. This is the major difference between SOQL and dynamic SOQL.

Dynamic query looks like this...
List<sObject> L = Database.query(string);

Thanks

[Parul]

SOQL statements evaluate to a list of sObjects, a single sObject, or an Integer for count method queries.

For example, you could retrieve a list of accounts that are named Acme:

<span> </span>List<Account<span class="operator">></span> aa <span class="operator">=</span> [select id, name from account where name <span class="operator">=</span> <span class="string">'Acme'</span>];

SOQL(Salesforce Object Query Language)
1)Using SOQL we can Search only on one object at a time.
2)We can query on all fields of any datatype
3)We can use SOQL in Triggers and classes.
4)We can perform DML operation on query results.

SOSL(Salesforce object Search Language)
1)Using SOSL we can search on many objects at a time.
2)We can query only on fields whose data type is text,phone and Email.
3)We can use in calsses but not in Triggers.
4)We cannot perform DML operation on search result.

There are 2 types of SOQL Statements.

Static SOQL:

Static SOQL means you are using some SOQL with any user input or hard code values like below query view source
List<Account> lstAccount = [select id,name form account where name =’Amit’];
Dynamic SOQL:

Dynamic SOQL refers to the creation of a SOQL string at runtime with Apex code. Dynamic SOQL enables you to create more flexible applications. For example, you can create a search based on input from an end user, or update records with varying field names…..this is the major difference between soql and dynamic soql

 

dynamic query looks like this…
List<sObject> L = Database.query(string);

[Parul]

The following items use an implicit namespace for your organization and don’t require you to specify a namespace.

References to custom objects
References to custom fields on standard and custom objects
References to Apex controllers

[Parul]

Reference a JavaScript library that you’ve uploaded as a static resource, use a <ltng:require> tag in your .cmp or .app markup.
The framework’s content security policy mandates that external JavaScript libraries must be uploaded to Salesforce static resources. For more information on static resources, see “Static Resources” in the Salesforce online help.

Here’s an example of using <ltng:require>.
<ltng:require scripts=”{!$Resource.resourceName}”
afterScriptsLoaded=”{!c.afterScriptsLoaded}” />

 

hope this helps you!

[Parul]

Adding some points:

Reference a JavaScript library that you’ve uploaded as a static resource, use a <ltng:require> tag in your .cmp or .app markup.
The framework’s content security policy mandates that external JavaScript libraries must be uploaded to Salesforce static resources. For more information on static resources, see “Static Resources” in the Salesforce online help.

Here’s an example of using <ltng:require>.
<ltng:require scripts=”{!$Resource.resourceName}”
afterScriptsLoaded=”{!c.afterScriptsLoaded}” />

 

hope this helps you!

[Parul]

Adding more points:

Here’s an example of using <ltng:require>.
<ltng:require scripts="{!$Resource.resourceName}"
afterScriptsLoaded="{!c.afterScriptsLoaded}" />

[Parul]

To reference a JavaScript library that you’ve uploaded as a static resource, use a <ltng:require> tag in your .cmp or .app markup.
The framework’s content security policy mandates that external JavaScript libraries must be uploaded to Salesforce static resources. For more information on static resources, see “Static Resources” in the Salesforce online help.

[Parul]

navigateToMyComponent : function(component, event, helper) {
var evt = $A.get("e.force:navigateToComponent");
evt.setParams({
componentDef : "c:myComponent",
componentAttributes: {
contactName : component.get("v.contact.Name")
}
});
evt.fire();
}

[Parul]

rerender():
It allows the component to update themselves, when other component updates since they were last rendered. It doesn’t return any value. It automatically called when data is updated in the component. Call superRerender() to chain rerendering to the components in body attribute.
Example:

rerender : function(component, helper) {
this.superRerender();
// Write your custom code here.
}

Hope this helps!

[Parul]

rerender():
It allows the component to update themselves, when other component updates since they were last rendered. It doesn’t return any value. It automatically called when data is updated in the component. Call superRerender() to chain rerendering to the components in body attribute.
Example:

rerender : function(component, helper) {
this.superRerender();
// Write your custom code here.
}

[Parul]

rerender():
It allows the component to update themselves, when other component updates since they were last rendered. It doesn’t return any value. It automatically called when data is updated in the component. Call superRerender() to chain rerendering to the components in body attribute.
Example:

rerender : function(component, helper) {
this.superRerender();
// Write your custom code here.
}

[Parul]

The two main steps to build a dashboard are as follows:
Select the component.
Select the data source.
There are seven types of charts supported by Salesforce dashboards:

Horizontal bar chart

Vertical bar chart

Line chart

Pie chart

Donut chart

Funnel chart

Scatter chart

[Parul]

A user can access dashboards from the Dashboards tab, depending on the dashboard folder permissions and user permissions. One dashboard can contain up to 20 components. Each component can be present in the form of a chart, table, or matrix. On top of that, you can also select the Visualforce page component type.

We will not discuss the Visualforce page as a component in detail in this book; this is just additional information. When standard components that are provided out of the box do not fit your requirements, use Visualforce page is an option.

[Parul]

Beyond setting the organization-wide sharing defaults for each object, you can specify whether users have access to the data owned by or shared with their subordinates in the hierarchy. For example, the role hierarchy automatically grants record access to users above the record owner in the hierarchy. By default, the Grant Access Using Hierarchies option is enabled for all objects, and it can only be changed for custom objects.

To control sharing access using hierarchies for any custom object, from Setup, enter Sharing Settings in the Quick Find box, then select Sharing Settings. Next, click Edit in the Organization-Wide Defaults section. Deselect Grant Access Using Hierarchies if you want to prevent users from gaining automatic access to data owned by or shared with their subordinates in the hierarchies.

Hope this helps.

[Parul]

It is not possible , by default Grant Access Using Hierarchies options are enabled for standard objects and they can not be changed. For custom objects we can change “Grant Access Using Hierarchies “settings .

[Parul]

Territory Management. Territory management is an account sharing system that grants access to accounts based on the characteristics of the accounts. It enables your company to structure your Salesforce data and users the same way you structure your sales territories.

[Parul]

Adding some points:

A bare repository is nothing but the .git folder itself i.e. the contents of a bare repository is same as the contents of .git folder inside your local working repository. Use bare repository on a remote server to allow multiple contributors to push their work.

Thanks

[Parul]

git fetch really only downloads new data from a remote repository - but it doesn't integrate any of this new data into your working files. Fetch is great for getting a fresh view on all the things that happened in a remote repository.
Due to it's "harmless" nature, you can rest assured: fetch will never manipulate, destroy, or screw up anything. This means you can never fetch often enough.

git pull, in contrast, is used with a different goal in mind: to update your current HEAD branch with the latest changes from the remote server. This means that pull not only downloads new data; it also directly integrates it into your current working copy files.