Skip to main content social and mobile offerings from Dreamforce

Did you see the tweets of #DF11 in your timeline? Did you happen to see large posters of Microsoft, balloons of Oracle floating around in Sfo? If you still didn't know what was going on, it was annual Dreamforce conference, which this year saw nearly 45,000 people registering for the event from over 60 countries, according to a Salesforce media statement. This turned to be the largest conference in the software industry. Obviously, if you have anything to do with Salesforce, you would know all this. If you are not, you have definitely heard of it.

It was a futuristic step to deploy a enterprise based CRM on Cloud and yet even after a decade, Salesforce keeps itself way way ahead of the competitors (are there any left now?) in again releasing a futuristic enterprise application.

The key take away from the entire Dreamforce 2011 conference was social and mobile. Salesforce opening the gates for a full fledged enterprise SCRM, where conversation and your leads rest in the same cloud. This Dreamforce, as with all the Dreamforce some more amazing new products where launched.

Social Apps:

1. Chatter Now: Chatter now is a real time chat feature for customers using Chatter. A good idea and many clients were asking for this feature.

2. Chatter Customer Groups: This is a unique concept, users can invite customers and clients in a secure and private chatter.

3. Chatter Approvals: Approval process now have context, where you can upload document and comments at all steps. What is more, users can approve records directly from chatter without leaving it. This is good because chatter feeds is easily available and I can just think of all the possibilities of manipulating the feed into the array of devices. Oh wait, there are already chatter apps on all the platform.

4. Chatter Connect: Chatter connect is a REST Api that can be easily used to integrate into third party applications. It can be used to make any custom mobile app and enterprise app social. Now, that is something very interesting. They also introduced, Chatter for sharepoint, finally lets hope sharepoint is a less boring and interesting.

5. Heroku for Java: The only drawback of Apex and Visualforce was that, it never received a good response from the developer community at large. It is understandable because normally developers look for big, big programming codes and apex achieves a lot in very less code. So with Heroku for Java developers, Salesforce is trying to get approval from the developer community. Heroku is amazing.

1. The world is going touch, Salesforce is no different and they also launched a touch version of CRM. One very good feature of touch system is, it works online as well as offline. Also, existing mobile applications will automatically mobile ported plus developers can create robust mobile application.

2. Seesmic CRM for Android: This is not exactly a Salesforce product announcement but a announcement by Salesforce partner, Seesmic. Seesmic has always provided amazing social apps (they were also the one to provide a mobile app for Ning network) and now they have come with complete Salesforce CRM for android. I have used it and it looks amazing for now. Will come with a detailed report soon.

1. I really want to know where they get these domains or how much they pay for it. But Salesforce has launched Data as a Service, which provides customer data from Jigsaw and D&B. Its just jigsaw with a fancy new domain name.

2. is now generally available, anyone can use it and create a database on cloud, which is also mobile and social.

3. Data Residency Option: has taken a step down with this announcement. does not fully run on public cloud but users now have option to take the data with them on their private servers. Giving a sense of hybrid cloud for their use.

These are pretty interesting product announcement by Salesforce. The company has again proved its way ahead of its competitors. There were other announcement also, like Siteforce now generally available soon etc.


Popular posts from this blog

The curious case of the custom redirection on Salesforce Console

Every developer worth their salt knows that the easiest way of redirection from a page to another is by using everyone's favorite function

public PageReference redirect() { PageReference pageRef = page.peskyProblemRedirection; pageRef.setRedirect(true); return pageRef; }
And the method is called by adding it to the Action attribute of the CommandButton or link, which works like charm and the user is redirected to the page after completion of the action.
So why am I going back to the basics? Because this way of redirection causes a pesky little problem in using the Service Cloud or Sales Cloud console.

Let's illustrate the problem, let's say you have a visualforce page as follows:

<apex:page sidebar="false" showHeader="false" controller="myExampleController"> <apex:form > <apex:pageBlock > <apex:pageBlockButtons > <apex:commandButton action="{!Redirect}&qu…

Some PDF tricks on Visualforce: Landscape, A4, page number and more

The beauty of Visualforce is simplicity. Remember the shock you received when you were told the entire page renders as PDF if you just add renderAs=PDF to the Page tag.

For those who thought I spoke alien language right now, here is the trick, to render a page as PDF, we add a simple attribute to the <apex: page> tag

<apex: page renderAs='pdf'> This will render the entire page as PDF.

Now, say we need to add some extra features to the PDF. Like a page number in the footer or we need to render the page in landscape mode. Faced with this problem, I put on my Indiana Jones hat and went hunting for it in the vast hay-sack of the internet (read: googled extensively). Imagine my happiness when i found a big big page with many big big examples to solve the problem. The document I am referring to is from W3C, paged Box media.

Long story short, I now possess the ultimate secret of rendering the page in any format I want. So here are few tricks I learned from the page. To p…

Cache me if you can: What you should know before daring to set URL parameter on visualforce

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…