Skip to main content

My Favorite Winter '15 features by Shivanath Devinarayanan

Out Guest Ninja for the day is MVP Shivanath Devinarayan from Unlimited. Shiva is talking about his favorite Winter 15 features. Handing it over to Shiva

My Favorite Winter '15 features 

  1. Duplicate alerts and blocking - One of more requested features, but yet not in full power yet due to the Beta release. It embraces the side of Salesforce; you will be allowed to setup rules on how to identify duplicates and will have full control on the process. Currently available for Accounts, Leads and Contacts.  Read more:  (
  2. Queuable interface – Now you can have total control over how your Async jobs are processed, with the new Queuable interface that your Apex classes can implement, you can enqueue jobs that you need to process, like insert a bunch of accounts.  Read more: (
  3. Customize Community with Community Designer – Gone are the days where you needed to be an HTML ninja or Visualforce master to have a sharp looking community-landing page. The Community designer is a point and click, drag and drop way to change your community’s branding and design to look smashing! Read More: (
  4. Territory Management 2.0 – Salesforce’s Original territory management lets you segregate territories based on criteria like postal code, revenue etc. But Territory Management 2.0 takes it up a notch by introducing components like Territory Models, Territory Types & Territory Model States. You can try and preview all the possible models before you implement it to ensure maximum coverage. NOTE: You can’t have customizable forecast along with Territory Management 2.0. Read More: (  
  5. Territory Triggers!  - I like this one personally, now you have more control to execute logic when the territory changes or if a user is added/ removed from a territory. More easier to notify people when they have a new territory to take care of.  Read More: (http//
  6. Lookup on activities (beta) – Alright maybe this one is my favorite, Even though this feature is in Beta I still feel it’s really helpful. Now you can create a custom lookup field on activities. Right now you can just add one lookup, but hey it’s better that not being able to add any. Read more (
  7. Access Permission sets in Formulas – Another very useful yet missing piece of the Salesforce world till now, you can access permission sets in the formulas. This is especially useful when you have a validation rule that you need to exclude for a certain set of people with this permission set.  Read more: (
  8. Salesforce Files Connect – With this new feature, now you can bring in your external files from Sharepoint Online. It works for both on premise and cloud setups as well. Another neat point is that you can add these external files to the federated search. Read More: (
  9. Ask questions in the chatter feed – I can see this being useful in the Success community or if your Org uses chatter extensively to collaborate. Instead of posting it in the answers forum your knowledge forum, you can ask questions directly in chatter, and if it gets solved it can be marked as the best answer. This will help in the engagement and adoption of chatter more. Read more: (
  10. Specify Session time out & password policies for individual profiles – A blessing for most of the admins, now you can set specific Session Settings and password policies for individual profiles previously which applied to the entire ORG. Read more: (


Wait element in flows – Flows have been the rising star in the Salesforce world. They’ve become more powerful over the last couple of releases. This feature now adds another feather to the cap; you can now have a wait element in trigger ready flows. You now can make the flow wait some time before you continue the remaining actions, and the best part is, its conditional, you can define when the wait element needs to be activated. E.g. one day after contract is activated.  Read More: (

What are your favorite features this release ?


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…