Skip to main content

Summer 10 Chatter in the cloud

Salesforce.com has done it again, coming in Summer 10, we take a exponential leap onto cloud and a brand new chatter application, openSocial web starts making sense.
With Chatter you can follow your objects, records or even users. Its just like twitter on steroids, with twitter anybody can make a tweet, in chatter its everybody in your own organization.
You can follow records, objects and applications using a simple click of a button on the chatter section of the page.

After that all the changes you follow can be seen on a single page, your dashboard.
E.g.,
You can now follow individual records and see if they have changed:
I wish to track changes on the opportunity and want to follow it through the stages, all I do is click on 'follow' of the opportunity record.
Also, I follow a certain case which was previously owned by me but now is transfered to someone else.
I can keep a track of the items I want to follow, next time I login, and the case is closed or the opportunity has advanced through a stage..
I see both of them on my dashboard. This will help the business users or even managers to keep an eye on the records they are interested. This is a good idea for the manager who wishes to be in loop while dealing with a big client. No need to ask for reports on what is happening, he has all of it on his own dashboard.
Some of the interesting features looking forward in the release:
Force.com – Chatter Platform :
Chatter gets a free upgrade this summer with integration with the custom cloud. Now you can follow custom objects, custom application, integrated applications using chatter.

Your own Domain:
Coming this summer your organization will have a unique salesforce.com URL for all your access. This will be benificial for branding of the organization. Currenlty with existing URL structure, salesforce runs on ServerURL.salesforce.com and visualforce runs on c.serverURL.salesforce.com
What we can understand from this update is all of this will run under same sub domain yourdomain.salesforce.com. Incidently on the updates page, there is no detail information on this update. So we should wait and watch whats coming.
Dependent Picklists for Pages
Finally its here, I voted for this update. The greatest of the dependent picklist are now available on Pages. No more need for multi-level picklist.
Sites Single Sign-On
Using the same login you use in Salesforce.com application (http://login.salesforce.com/) you can now access sites and other custom domain application. Single-sign on will be benificial for throwing away those memory pills you have to take to remember countless passwords and login ids. One ID and you are done.
Cookie Support
Its here, its here. Cookie support will enable developers to build complex applications that needs to store a cookie on the application.
Dependent Lookups (beta)Every salesforce user has faced the need a dependent lookup. If I have to add a account and a contact in a single page, why on earth will I need to select again from the list of contacts, I should only see those which are child of the account which is selected. This has come in Beta mode, meaning we should expect this to contain bugs and hope for update in next release. Well, something is better than nothing, I can now show the client that this can be done and make him feel at ease at least.
As I had mentioned earlier 2010 began with Apple and Google failed to cause a big dent in the Universe, I am sure Chatter will. Atleast so far it seems they will, only time will decide if chatter is here to stay, for Salesforce Sales Cloud and Service cloud have a great usability so far, cannot say the same for collaboration cloud coming this summer.
May the force be with you,
Ravan

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…