Skip to main content

My Favorite Salesforce Spring '11 Feature

Man is a social animal. That is one thing man is sure about history, rest all is still a mystery. Once upon a time, man invented fire, to socialize with his friends at night. Then many million years later, people build houses countries and stuff and then he thought, what the, my friends are gone, whom will I socialize at night? And thus he invented the internet... true story. Well, not exactly true, but who cares, we are social now.

When I wake up early morning, I no longer check if there were any mis-cals last night, I also check if there were twitter mentions, facebook notifications for me. And my android facilitates all this with a single swipe of my thumb. The bottom line, we are social. And if you still don't have a internet line on your computer, you probably are still living in caves.

So Salesforce has grown, grown large like a big puppy and oh, it has also learned some new tricks. The latest release of Salesforce spring 11 boast of more social, more mobile, more success. Oh well, after the big bang of and at the Dreamforce 10 (read about keynotes here) this was expected of Salesforce and must say, so far, we are not disappointed.

So my favorite Salesforce Spring 11 features:

1.   Apex Governor Limits:
-The total number of DML statements issued for a process has gone from 20 for triggers, and 100 for everything else, to 150 for all contexts.
-Total number of records retrieved by SOQL queries has gone from 10,000 to 50,000
Do I see developers rejoicing?

2. Chatter Updates:
Oh well, Chatter has gone the twitter way and now we have @mentions the #hastags as well as Like button.

3. Visual Workflow

Now, this is a feature I would like to know more about. From the look of it, it looks like another computer software to replace me.... sigh.... still, since I used Appinventor development without coding, I feel I might like this. Still more on this later.

4. REST Api
Coming Spring 11, REST Api will be generally available and now you can connect to SFDC using OAuth protocol. To dig deeper on rest API, you should probably dig deeper here.

5. Google Chrome Support for Salesforce
This was the massive idea on IdeaExchange and even I had voted for it. Glad to see it there.

6. Visualforce Pages Inline Editing
Aaah, finally, one attribute that will support Inline editing, no need to play with ActionSupport OnClick event and rendering events. So far release notes say that there are two forms of inline editing support: the <apex:detail> component has been enhanced to support inline editing, and the<apex:inlineEditingSupport> component has been added, which gives inline editing functionality to several container components. More on this soon.

7. Visualforce Dynamic Binding
I have not yet fully understood this feature but the demo looks awesome. I will write another blog post for VF enhancements soon.

8. Javascript Remoting
Now we can directly call Apex classes in VF using Javascript and @Remoting call.

@RemoteAction global static String getItemId(String objectName) {
 /* ... */

Nice isn't it?

There are many more enhancements coming to us this year. With so many bangs at the beginning of the year, we should expect more adrenalin rush the complete year, isn't it?

Just, Fyi, I have build my first app on android, will share the Apk with anyone who is willing to test it. Now going for a full blown app to host on the market, keep fingers crossed.


P.s. Moved my signature from Sidoscope here. How is it?


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…