Sunday, 17 September 2017

How can India Dreamin be technology connector for students?

Being a College student, I might not have heard the technology named Salesforce, but the buzz on the Internet of the event as ‘India Dreamin’ made me google it out. There was some amazing post on #SFDC4Students which made me keener to go around.


India Dreamin provides interactive, hands-on workshops, seminars, and activities for college students seeking to gain valuable exposure in leading-edge technology topics. This event gives students the opportunity to network with young entrepreneurs and other youths from around the country who are pursuing academic and professional futures in the Salesforce technology industry.



Technology alone cannot help the students unless you get proper guidance.

I found college students at campuses across the globe admitted being “addicted” to modern technology. This is where India Dreamin would play the best role in their life.

India Dreamin is an enormous Event, who is giving me the opportunity to have a lifetime experience of communication with such a great set of the young crowd.

Don't forget to take a sneak peek of the event via twitter or website.

Listen to inspirational talks from Industry leaders around tech subjects.
Every Star Speaker is a Salesforce champ and has been contributing to the community in their unique way. Getting connected with such extraordinary people would be an opportunity we just can’t miss.




As I'm myself in my early twenties, it is surely a huge opportunity for me to present myself as a Volunteer in front of the pupils. In the event, it is important for me to have an interactive session with the students and be a resourceful adviser to each one of them. 


The highlight of the event that I am eagerly looking forward is the rapport and the compatibility that will be created on the premises with the support of the students. I am thrilled to engross myself with everyone present there and be my best to guide them with their queries related to career and similar points.

Spot me and let’s have a chit-chat about Salesforce.



Saturday, 26 August 2017

Time To Upvote -Series (Part 3)

In case you missed the first two blogs :





Here we have some idea's which need to be upvoted :

IDEA 1 - 

Enable drag & drop functionality for lightning Calendar

Salesforce classic calendar supports drag & drop off events.
Lightning has a much more dynamic user interface, but it still lacks this basic functionality which keeps many customers from managing their calendars entirely in Salesforce.

Upvote

IDEA 2 -

Allow new chats to load in the background, without monopolizing agent focus

Current behavior: When a new chat is accepted, the new chat monopolizes the agent focus, and the agent is not able to continue chatting or performing after-chat work. It brings the agent to the new chat tab, even though it takes ~ 5 seconds to load all 3 chat sub-tabs (chat, contact, case). Even once the 3 chat sub-tabs load, the user often takes a while (sometimes up to a couple minutes), to type out their question, so staying on the new chat tab is not usually the best use of agent time.
Desired behavior: When a new chat is accepted, the new chat should load in the background, allowing the agent to continue working on the other chat(s) they have open. The new chat should *not* force the agent to sit there and watch the 3 chat sub-tabs load. After working a little more on the open chats, the agent can check back on the new chat, and see how far along the customer is in composing their question. This is less disrupting to the agent workflow and maximizes agent control and efficiency. 
Note: We've been told by the Live Agent PM that this is desired/expected behavior of the product. However, having observed agents in the field using Live Agent over the course of 1 week, I am confident that this is not desired behavior, and it is much preferred that the new chat *not* monopolize focus, and force the agent to sit there and watch the 3 sub-tabs load.





IDEA 3 - 


Allow Direct link to a Process Builder Process

When working with clients and/or other admins I need to be able to reference the specific process builder that I would like them to look at.  Right now the link available to me is the link that displays all of the process. 
Ideally, we should be able to send a link that opens up to the specific process.  This could be something similar to what is available in the Service 


IDEA 4 - 

Pardot Merge Prospects via API

Hi All,
I've gone through the pardot API documentation, but have not found anything related to merging/deduplicating pardot prospects through the pardot API. We have a scenario where we are getting a lot of duplicates in our pardot instance. And also we have defined criteria of considering which of these prospects are duplicates.
Since this number is huge, we wouldn't want to spend hours manually merging all of these duplicate prospects. Would be glad if Pardot rolls out an additional method within its APIs.
Please vote up this idea if you're facing the same issue.

Please refer the following link - https://success.salesforce.com/ideaSearch




Sunday, 16 July 2017

Ctrl + Z - Setup Audit Trail

Control + Z is a used to undo the last change done during typing any code, or vice -versa.
What would be Control+Z when it comes to Salesforce?




Salesforce.com keeps an Audit Trail of configuration changes made in the Setup section. This Audit Trail is available for administrators to track recent setup changes. This becomes especially helpful if there are multiple administrators for your organization. 

Steps To View Setup Audit Trial: 




 Navigate to Setup | Administer | Security Controls | View Setup Audit Trail: 







The preceding screenshot shows the last 20 most recent configuration changes for your organization.


The Audit Trail is useful for troubleshooting. Because it captures date/time, you can often trace user issues back to a specific change. For example, if users all of a sudden are being asked to reset their passwords, you can trace that back to a change in password settings.

To download your organization’s full Setup history for the past 180 days, click the Download link. This will give you a CSV file that can be opened in Excel and sorted.

Starting with Winter'16 the SetupAuditTrail object (https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_setupaudittrail.htm) has now been exposed via the Salesforce API's and within Apex via SOQL.

Have a look at Andy in the cloud blog about SetupAuditTrail object .



Audit Trail key concepts:

You can check Audit Trail for the mentioned section/type of changes:
Administration: This will track sundry administration changes such as vicissitudes in the company information, multiple currencies, users, electronic-mail address changes, profile changes, roles, record types, engendering e-mail footers, and domain name changes.

Customization: These vicissitudes are cognate to the interface changes, forecasts, contracts, conceptions, field tracking in victuals, support-cognate settings, process setups, and transmutes to groups.

Security and sharing: These are cognate to security settings and sharing, such as password policy changes, session setting changes, vicissitudes in SAML settings, and so on.

Data management: These vicissitudes are cognate to the mass expunction of records, data export requests, the mass transfer of records and import wizard utilization, and transmutes in analytic snapshots.

Development: This change is cognate to Apex classes, triggers, and Visualforce. Changes can include modifications to triggers, classes or Visualforce; remote site access setup; and Force.com site setup.

Sundry setups: These include sundry setup changes such as the engenderment of an API, utilization metering notifications, territories utilization, workflow and approbations settings, and AppExchange package installation/uninstallation, and engenderment and effacement of workflow actions are additionally tracked.

Utilizing the application: These transmutations are cognate to the vicissitudes in the account team and opportunity team selling settings, Google App accommodations, and the enabling and incapacitating of partner and customer portal users.


References: https://help.salesforce.com/articleView?id=admin_monitorsetup.htm&type=0



Monday, 19 June 2017

Salesforce Essentials - 27(Call from developer console to batch class and Schedule Batch class)



Steps to call batch class and  Schedule Batch class from Developer Console - 

 




In order to run batch process, you need to use
Database.executeBatch() method.

accountBatch btch = new accountBatch();
Database.executeBatch(btch); 

accountBatch - is your Salesforce Batch Class .







You can schedule this class for a particular day and any specified time at which the class can be run. Using this declarative way, the highest frequency we can have is once per day within Salesforce and not more than that. 

With the system.schedule we pass parameters:
system.schedule (Name_of_job, Time_for_scheduling_job, Schedular_class_name)


This class is scheduled to run at 12 AM, on the 31st of Dec.




You can Check the scheduled batch classes:




References :https://help.salesforce.com/articleView?id=000171199&language=en_US&type=1



Thursday, 25 May 2017

Salesforce Essentials - 26(Limitation of Lighting Professional edition in Salesforce)




Lighting Professional Edition in Salesforce

There are few features which are not available in the professional edition which needs to take care during implementation:


No Account Assignment Rules
No Territory Management
No Sales Teams (aka Opportunity Teams)
Configuration / Security / Administration
No Joined Reports
No Bucket Fields
No Cross Filters (e.g. Accounts without Opportunities)
No Dynamic Dashboards
No Scheduled Dashboards (you can schedule a Report)
50 Custom Report Types vs. 200 in Enterprise Edition
See our post on Enterprise Analytics for more details on these features
Marketing

250 emails sent in a single mass email blast vs. 500 in Enterprise Edition
Sales (Sales Cloud)

Limit of 20 Custom Fields on Activities vs. 100 in Enterprise Edition
Limit of 10 Custom Tabs vs. 25 in Enterprise Edition
Limit of 50 Custom Objects vs. 200 in Enterprise Edition
No Workflow / Approvals / Visual Workflow
No Person Accounts
No Ability to mass Grant Login Access to a System Administrator
No Data Export (Weekly Export Service to backup your Salesforce org)
Support (Service Cloud)
Limit of 20 Validation Rules per Object vs. 100 in Enterprise Edition

Limit of 100 Custom Fields per Object vs. 500 in Enterprise Edition





No Service Cloud Console
No Salesforce Knowledge (Note: Knowledge is available at an additional cost in Enterprise Edition, and included in Unlimited Edition)
No Live Agent (Note: Live Agent is available at an additional cost in Enterprise Edition, and included in Unlimited Edition)
Extending Salesforce / Community / Portals

No Partner or Customer Portal
No Websites (aka Site.com / Force.com Sites)
To use Chatter Plus (Chatter Only) licenses in Professional Edition, you’ll need to contact Salesforce support and have Profiles enabled
No Salesforce Communities (released Summer ’13)
Custom Development and Sandboxes

No Change Sets (which are needed to deploy custom code)
No API (thus no ability to use the Data Loader or build custom integrations)
No Partial Copy Sandbox
Limit of 10 Developer Sandboxes* (*Change Sets disabled) vs. 25 in Enterprise Edtion
Lightning Professional Edition Limits

5 Process Builder processes
2 Permissions Sets
2 Custom Profiles
3 Record Types
2 Page Layouts
10 Developer Sandboxes


Download the full edition comparison chart 


Try the world’s #1 CRM solution free for a full 30 days. Sales Cloud — Lightning Professional Edition

A detailed difference between the features available and variations of these features in each of the editions is available on http://login.salesforce.com/help/doc/en/limits.htm.

You can understand the pricing on http://www.salesforce.com/in/crm/editions-pricing.jsp.

References:
https://www.salesforce.com/in/editions-pricing/service-cloud/
https://www.shellblack.com/administration/differences-between-professional-edition-and-enterprise-edition/

Monday, 22 May 2017

Salesforce Essentials - 25(Magic Stick for Beginners - Developer Edition "DE org")

Development and deployment on Force.com typically take place in an environment or org, which provides a number of features and accommodations for applications within that environment. An environment lets you instantly start developing, testing and deploying your app in the cloud. For an explication of the types of environments, optically discern An Exordium to Environments.



Follwing are the salesforce licenses : 

Salesforce Customer Portal
2 Salesforce CRM licenses
2 Salesforce Mobile licenses
3 Salesforce Platform licenses
5 Salesforce Partner licenses
10 Salesforce Customer Portal Manager licenses  


Other Limits for Developer Edition:


5.0 MB of Data Storage
20.0 MB of File Storage ( attachments)
5000 API requests per 24 hours
Any number of applications
A 500 MB bandwidth and 10 minute service request time limits (per rolling 24 hours) 


Developer Edition (often referred to as a "DE org") is a fully-featured development environment with limits on data and users. Developer Edition is used for:

Trailhead - Salesforce's free and fun online learning tool requires Developer Edition.
Development and Testing - If you don't have a sandbox (a copy of your Salesforce production organization), you can use Developer Edition to isolate development and testing.

ISVs - Independent Software Vendors use DE orgs to create managed packages, which may then be released as apps on the AppExchange.

Developer Previews - Sometimes we release new functionality to Developer Edition before other editions, so you can practice with it.


Fun - You can have more than one Developer Edition, so use one whenever you want to mess around and try something new.





How to signup for free developer edition in Salesforce?




1. Open "http://developer.force.com/".
2. Click "Sign Up" button.
3. Fill in the details. Click "Sign me up". 
4. Verify the account in email.
5. Use "https://login.salesforce.com" for login.


References :


https://developer.salesforce.com/page/Developer_Edition
https://www.quora.com/What-are-the-limitations-of-a-Salesforce-free-developers-account





Thursday, 18 May 2017

Salesforce Essentials - 24(Different Types Of Sandboxes)

Sandboxes :

A sandbox is a replica of an engenderment environment utilized for a variety of purposes, commonly including testing and development. Here's how it works: When you engender or refresh (essentially effaces and reconstitutes a sandbox utilizing the same name) a sandbox, a facsimile of the engenderment environment at that point in time is made.




different types of Sandboxes 

1) Full Sandbox - Plenarily testing changes against authentic data afore promoting to engenderment.  This may include utilizer acceptance testing.  All changes must go through this sandbox.  If multiple admins/developers are working on overlapping areas, this is the place where changes get merged.  Force.com IDE can be habituated to compare changes by separate developers of the same apex code.

Full sandboxes have the same storage limit as your production organization.

Once you refresh the Full Copy Sandbox then to refresh it one more time you have to wait for 29 Days.

2) Partial Data Sandbox - This is an incipient sandbox type and I am not quite sure what the intention was.  Probably just a more frugal alternative to a full sandbox.  If you have a full sandbox, then partial data sandbox sounds like a good place for utilizer training for incipient features, incipient employees, etc.  Having authentic data can authentically avail with training.  Additionally, possibly a place to work on integration changes since it can hold quite remotely of authentic data.

Partial Data sandboxes have a 5 GB storage limit.

Once you refresh the Partial Data Sandbox then to refresh it one more time you have to wait for 5 Days.





3) Developer - A place to work through solutions to incipient requisites.  The main conception is to keep arbitrary experimentation out of the full sandbox.  It there are multiple admins/developers, each one should get their own so that they don't trample on each others work (until they deploy to the full sandbox).

Developer sandboxes have a 200 MB storage limit.

Once you refresh the Developer Sandbox then to refresh it one more time you have to wait for 1 Day.

   


                                

4) Developer Pro - The main distinction between this and Developer is the amount of data that can be stored.  It additionally prehends some product data from engenderment.  If those two things are paramount, utilize this one.  Otherwise, it's interchangeble with Developer.

Developer Pro sandboxes have a 1 GB storage limit.

Once you refresh the Developer Pro Sandbox then to refresh it one more time you have to wait for 1 Day.


References : 

http://www.salesforcetutorial.com/introduction-to-sandboxes/
https://help.salesforce.com/articleView?id=create_test_instance.htm&r=https%3A%2F%2Fwww.google.co.in%2F&type=0




Saturday, 13 May 2017

Time To Upvote -Series (Part 2)

Here we have some idea's which need to be upvoted :



Idea 1 
Make the Manage External User button available in lightning

Currently the Manage External User button and the nested buttons it hosts are not available in the lightning user interface, as a result users have to switch between lightning and salesforce classic to access the functionality, another drawback to lightning as having to toggle back and forth between two different interfaces undermines the value of lightning.  Please make the manage external user button and the nested buttons it hosts available in lightning

Upvote 


Idea 2
Choose Who To Send Flow Fault emails and Process Builder Error Emails to

The notifications currently go to the user who built the flow or process builder.
I am currently in a situation where the original user who created the flows in Sandbox and deployed them is no longer active. I therefore must change his email in order to receive the error messages on existing flows.






Idea 3 
Increase the limit on the number of reports a user can subscribe to

The new report subscription feature is really nice, but only being able to subscribe to 5 reports is not helpful.  Most users who want to subscribe to reports want to do this for at least 10 - 15 reports.  I'm not sure why the limit is hard-coded to be 5 but having a higher limit (like 25?) would be much appreciated.


Idea 4 
Process Builder: Error messages

Process Builder works great, but when there is a validation error or any other error, it doesn't provide the much information to user and user will never know how to resolve that issue.
Admin gets an email for this exception with the proper message, but if we can improve the error messages for the end user also, that would be great.



Please refer the following - https://success.salesforce.com/ideaSearch





Saturday, 29 April 2017

Salesforce Essentials - 23(Batch Apex in Salesforce )

To use batch Apex, write an Apex class that implements the Salesforce-provided interface Database.Batchable and then invoke the class programmatically.
To monitor or stop the execution of the batch Apex job, from Setup, enter Apex Jobs in the Quick Find box, then select Apex Jobs.






It allows you to define a job that can be divided into manageable chunks, where each chunk can be proceed separately.

 Methods defined in batch apex class?

To use Batch Apex, you must implement “Database.Batchable”. This interface has three methods. those are:
1. Start
2. execute
3. Finish


 Return types and syntaxes of all methods of batch apex class?

 Start:

global (Database.QueryLocator | Iterable<sObject>) start(Database.BatchableContext bc) { }

Execute: 

global void execute(Database.BatchableContext BC, list<P>){ }
Finish:



global void finish(Database.BatchableContext BC){ }


Sample Code :

global class Accountupdate implements Database.Batchable<sObject>
{

global Database.QueryLocator start(Database.BatchableContext BC)
{
        String query = 'SELECT Id,Name,Phone FROM Account ';
        return Database.getQueryLocator(query);
    }

    global void execute(Database.BatchableContext BC, List<Account> scope)
    {
        for ( Account a : scope)
        {
           a.Phone='123';
        }
        update scope;
    }  
    global void finish(Database.BatchableContext BC)
    {
    }
}






When we need to go for batch apex class?
  • When you want to do a bulk job.
  •  To have higher governor limits. 
  •  We can schedule to run at different time.
References :

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_batch_interface.htm
https://developer.salesforce.com/forums/?id=906F0000000BOduIAG