Skip to main content

Spring 12 Salesforce Contains a Bug... a lady bug.


Its freezing cold out here. When I say its cold, I mean its cold, the cruel hellish humid city of Mumbai is also wrapped in the basket of coldness and finally after a decade, Mumbaikars (people from mumbai) have a topic of conversation with Delhites (people from Delhi) over cold. But while the entire world is still coping with the cold of winter, the clouds have already moved on to spring.

Salesforce has come out with the Spring 12 release and it contains a bug, no not software bug but a lady bug on the leaf. Obviously on the glorious traditions, new updates to not mean patches to cover up your mistakes, it means glorious new features and new things. As with the tradition with this blog, this is a feature to discuss top ten features that I find interesting in the update.

Chatter Now
Instant messenger inside chatter is now Generally Available. This is a good move towards turning into the one tool for Enterprise 2.0 collaboration platform. This can be the next Office Communicator Killer if used efficiently.

Social Contacts and Accounts
Salesforce kicked off last Dreamforce with a bold, 'Welcome to the social enterprise' it was obvious that Social Contacts and Accounts would be generally available sometime or the other. However, one beautiful addition to this is support for Klout and YouTube is added to it. This is a good step to move beyond the main stream social network and also a indication that this will expand beyond. If nothing else, you can see the picture of your contact, instead of a name.

Cross Object Workflow on Standard Object
With this release many standard objects are included in Cross Object workflow. Did I hear a sigh of relief from developers? Yes, this feature is bound to save a lot of coding time and create some beautiful processes quickly. However, currently only few Standard to Standard objects are included with limitation. But this gives a hope that in future we can expect some more features in it.


Workflow Field Updates Can Retrigger Workflow Rules
This looks amazing and was also one of the most critical interview questions. Can one workflow rule fire another workflow? Now the answer is yes. There can be 5 workflow in all which can be triggered one after another on field update. When there is a field update on a workflow, all the workflow rules are reevaluated, which did not previously meet the criteria. This is a very good update in terms of creating domino effect and will also reduce a lot of code while writing trigger.

Cloud Flow Designer is GA
With every passing update, coding is getting reduced less and less. Not sure if I like this or no. True, this saves a lot of time and we can utilize the time in designing killer system and leave the mundane task like making screens to the Flow Designer. But still, I miss coding. Fret not, I am sure most users will rejoice, now no need to tolerate the attitude of the developer, anyone can design screens on their own. Non-profits can benefit from this feature a lot as it is easy to use.

Chatter Answers

Chatter Answers integrates Cases, Answers, Force.com Sites, Customer Portal, and Salesforce Knowledge to provide you with a Web community for customers. This is also a bold move towards the Social Enterprise. We also are provided with Visualforce components to create these custom answers.

Live Chat Agent
An improvement to service cloud. Using the Live agent we can directly add live chat facility to the the public facing site. In additiaon to this feature, we get separate 8 components in visualforce to prepare the Chat Agent.

Apex Rest Api
Aah, finally, Apex REST automatically provides the REST request and response in your the REST methods via a static RestContext object. We can expose the Apex classes directly via Rest API.

Dynamic Visualforce Components are finally GA
This is my personal favorite update, dynamic components are very necessary for so many things. Wait till I dump those JavaScript and rework on the visualforce component using dynamic components. Similarly we also have dynamic bindings which can bind a variable to the controller.

Tab Bar Organizer
That annoying horizontal scroll which was not irritating for so many Salesforce edition finally is resigning. Now the overflowing tabs are neatly folded on the screen, also indicating that many developers are lazy organizing tabs in apps. This is a funny update but trust me in all the above, this is the most important update.

That ends my top ten list of Spring 12 update. Some parts in Spring 12 are very beautiful and I will try to cover as many as I can in upcoming blog. What is your favorite spring 12 feature?

Comments

Popular posts from this blog

Video: Top ten tips on how not to ruin Salesforce implementation

Another presentation for the London Salesforce Developer Group using mobile app. 
When it comes to Salesforce development, we all know what it takes to deliver stuff. Having a certified professional helps you gain a knowledgeable partner but what about the things such as common sense?  We all know how to deliver things on client requirements but what about things that are not mentioned by the client. We will be discussing in details things that will enhance the user experience, focus on tips to read your customers mind and have a bit of perspective on the user experience.

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…

Four secrets to improve the usability of your visualforce/Lightning pages on Salesforce

In the immortal words of a certain machine returning back in time, I am back. For now. After procrastinating for over a year and drafting a lot of rants- I am back with a very important coding lesson for you. For now.

When we are designing a Visualforce page or an app or a lightning component (added that only to trick google) or any web page for that matter, we often tend to wrap up things quickly. Ask anyone on the team, how to design a good User Experience? and the person will immediately throw buzz words like Bootstrap, angular and other useless libraries (did someone squint?)

Ok, Bootstrap, Angular-Js, and all the libraries are really cool and are useful in designing a fabulous UI. They are helpful in creating responsive pages that will work on all the devices but this post is not about those. Nope. For the purpose of this post, all the external libraries and buzzwords you use to decorate your resume are useless. (Adding Angular JS in your resume for a Salesforce consultant posit…