Yes, you have read it right. We would be integrating Salesforce & Facebook Messenger within 5 minutes without writing any single like of code.
This impossible task of integrating two systems seamlessly is done by Digital Engagement. If Digital Engagement is a new product for you, I would strongly recommend reading my previous post, where I covered it in a little bit more detail.
What do you need to set up Digital Experience?
You would need a business that you want to grow by leaps and bounce, its Facebook Page, Salesforce Service Cloud, and Digital Experience add-on license.
Once you got all these, the first step would be to enable Messaging and for that navigate to Setup | Feature Settings | Service | Messaging Settings and enable Messaging.
Amazon, Apple, Google, etc all trillion-dollar companies, what do they have in common? Their obsession for customer service & keeping customers at the center of your business.
It’s not only about trillion-dollar companies, but also medium and small businesses, if they want to succeed in this comparative market, they need to make sure customer service is at the heart of their business.
If I ask you a question, which technology gadget you cannot live with ? That’s your mobile phone and it is pretty much possible that you are reading this blog post right now on your mobile device.
So, if you are a customer and you have some issue, what are some of the options that you would like to use to contact companies? Phone calls are great but the problem is its real-time communication and you need to be on call with a customer representative and cannot do multi-tasking.
The email could be another option, but spammers, marketers they have flooded our email box and to be honest, I hate opening my emails, there are tons of unread email every day.
So, what point I’m trying to make here? I’m indirectly talking about channels and ways customers can try to connect to the company if they face issues. Phone & emails are out because of some reasons mentioned above. The few options which are left are Social media, Live chat, or SMS. Customers can do multi-tasking while using all these channels. They don’t need to be on call for 30 mins or 1 hour to get issues resolved.
That brings us to our blog post title, how can we use SMS in Salesforce to enable customers to reach out via text message? Today, we have lots of options like AppExchange products, Live Message and then there is the new kid on the ground – Digital Engagement.
In this post, I would be only talking about Generally available (GA) features, excluding pilots and Beta. Saving those awesome features for suitable time to come. So, here are some of my favorite picks from Spring 17.
Imagine we are doing REST API call from external system by creating Account first and then contact. In between if internet connection is gone or user closes browser and only Account created without contact ? From Spring 17, we can reduce number of REST API calls made by combining them in single request. Advantage of this feature would be easier transaction management and API limit saving. You can have up to 25 subrequests in a single call. Up to 10 of these subrequests can be query operations, including Query, QueryAll, and “Query More” requests to obtain the next batch of query results.
Below are short videos on how to get things done in Salesforce from documentation and user interface team.
Formulas are very powerful. They can help you to do everything from pulling informations from parent to child objects or caluclate something on basis of other field present on same record or parent record. Below are list of videos to make you more productive on formula.
While developing applications on Force.com platform using Apex, I am sure you may have been in need of debugging your code. Salesforce being cloud platform, method to debug code is very different as compared to other programming languages. In this post we will discuss all about Apex code debugging, challenges, solutions and other best practices.
This is first of many upcoming articles on evaluation of Salesforce AppExchange products. In this post we will be discussing capability of native Force.com based solution for Continuous integration. Deployment has always been one of pain point in Salesforce developement. I have worked and proposed many solutions to customers based on their requirement and budget. One of solution which got my attention recently is “Flosum” available and listed on AppExchange from this year.
I have used many traditional continuous integrations like Jenkins, Bamboo, Scheduled ANT script but all of them still involve manual intervention and most important, special skill set to setup and handle any issue arising time to time.
Let’s talk about Flosum and what makes it different at high level:
Complete native solution built over Force.com platform
Requirement gathering to deployment, all aspects covered
Multiple environment management
Easy Profile migration
Security access to environment for each user
Default space 11GB
Acts as Version Control
Supports Continuous integration and auto deployments
Compare Complete Org with historical or current changes
Does it takes a lot to view debug logs i.e. via setup area or dev console. This extension is an attempt to make this use case simple, by making debug logs visible in 2 clicks, without leaving the current Salesforce tab. Plus, you get a better hierarchical view of debug logs, which are better to analyse.
I have lots of expectation from this extension as this is the one of extension which takes feedback actively (You can find discussion tab just inside app) and frequently releases new capabilities. More features, like Execute Anonymous, Code Coverage, Test Cases are in pipe, will be released soon.
Second in my list is “Salesforce Navigator” and I cant live without it a single day. On average, it saves more than 50% of my clicks needed for administration. My shortcut for this utility is “Ctrl + Alt + Space” and I guess this most used combination on my system. Using this utility, you can directly navigate to any setup page like Object, Apex class, Pages, Workflow rule etc.
In many of my previous implementations I have used advantage of Apex code running in System mode however never tried how far it can go in terms of capabilties. There is no specific Salesforce documentation which can explain that what is allowed or not allowed in System mode.
In this post, we will go through some scenario and will try to understand what really is possible in Apex System mode and when it can fail.
Before diving more lets discuss how many types of mode do we have in Apex ?
User Mode :As per this Salesforce post, all Profile level permissions, sharing rules and Field level security are enforced in Apex if it runs in User mode. Standard Controller and Anonymous Apex runs in User mode.
System Mode :Same post conforms that custom controller, trigger, Apex class, controller extension works in System mode. Means eventhough user does not have necessary profile level permission, record level permission or field level permission, but still they can perform any operation on it.